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

[Salad]

Tony Ciconte wrote:

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?

I haven't. Hopefully someone else has and can help. If I understand
you correctly, when you close the app and it runs some cleanup code, it
leaves the app on the system tray. If you don't run it the cleanup code
it does not. Is that correct?

Do you do something like
If SomethingIsTrue Then Do Cleanup
Application.Quit

I can't imagine that using a macro to quit would make any difference.
That could indicate that something is not completing in the cleanup.
Maybe you could do something like
If SomethingIsTrue Then Do Cleanup
DoEvents
Application.Quit

If that doesn't correct, I would look at your cleanup code
Sub Cleanup
If This is true then
.....
endif
If that is true then
.....
endif
End Sub
Then put in
Exit Sub
immediately under the word Sub. Then run. Does it leave it in SysTray?
If not, move Exit Sub under the first endif. Then run. Does it leave
it in Systray? Keep repeating until you find the code section that does
leave it in Systray. Then scratch head, puzzle it out, and see if it
can be fixed.

[Terry Kreft]

Really to have any chance of answering this we need to see the code you use
for creating the references and your clean up code with comments to show the
difference between the working version and the non-working version.
--
Terry Kreft
MVP Microsoft Access

"Tony Ciconte" <to******@comcast.net> wrote in message
news:5j********************************@4ax.com...

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