Strange problem when quitting program after library reference updates?

[Tony Ciconte]

We have developed an Acc97 application and distribute it using the
Wise installation system and SageKey scripts. The installations are
rock solid and the product works well on all types of systems.
However, we have notice a peculiar issue when running on either
Windows 2000 or Windows XP systems. Specifically, the application uses
the OutLook libraries to move information back and forth to MS
OutLook. We check references when the application initially starts and
use code to fix any broken ones. This works well and the application
runs without problems except as follows.

When we exit the program the FIRST TIME ONLY (after the refs were
updated), we get an item in the system tray that shows a window
stating that the app had a compile error and could not close. This is
odd since the app has closed and can be re-opened, closed, and used
properly as many times as required. The tray item seems to have no
effect on the application but it is a little disconcerting to the user
since the only way to get rid of it is to use the Task Manager.

There is a small routine that cleans up user information and close
open objects when the app closes. If we bypass this routine and/or any
other code and simply use a macro with Action=Quit, the app will NOT
leave this tray item. Has anybody seen this type of behavior before
and/or know how to stop it?

Any and all assistance is appreciated.

Tony Ciconte
DSI

 

[david epsom dot com dot au]

I'm not surprised that Access will fault internally if you change
references, but I've never seen a system tray item.

Are you running some kind of special fault detection software?

(david)

 

[Tony Ciconte]

David,

Thanks for the response. I am not running software other than a small
proc to reset the users logon flag in an attached table. It will do
this if I use ANY code to exit the program. For example, a simple
module that has only one instruction

DoCmd.Quit

will leave the same tray item an with a nasty note, when you maximize
it, saying the program had a runtime error. Clicking on the OK button
on that screen only minimizes the screen. However using a macro with
the "Quit" action closes the program properly without error and leaves
not tray trash.

I am not supprised about Access either but I do not remember my users
having this problem when they were using NT on their workstations.

TC