>Force of habit, Bruce - someone might pop off the Windows Shutdown dialog, or try to terminate the application using Task Manager, both of which result in Windows Mesages that would try to get the app to kill itself. I'm sure all your end-users are careful to exit all apps before installing something that requests a reboot...< BEG >

Ah, I see what you're getting at. Normally (not that this often happens), in my apps, you will get a "Cannot Quit vfp" message if that type of abortive exit occurs, and the app pops up, so the user must close it. And deal with any "Unsaved data" type messages, also. The other ON SHUTDOWN proc commands are not needed, they still work as normal within a top-level, since it must still be closed by user.

But you've got me thinking about it now - I guess the ideal situation would be to not use the ON SHUTDOWN for anything except QUIT, but to check for unsaved data first, and get rid of that "Cannot Quit vfp" message.

A little project to work on, to get the right sequence of events...

Here's a puzzle for you, though - I put ON SHUTDOWN QUIT in a TL. I run app, leave it open, and try to shutdown/logoff machine. Guess what? Nothing happens, except the app closing. The shutdown/logoff get aborted. Why would that be?