• Home
 · 
• Windows System Services
 · 
• Let your application close orderly before the system reboot. Avoid hanging the O/S while your appli

Let your application close orderly before the system reboot. Avoid hanging the O/S while your appli

Let your application close orderly before the system reboot. Avoid hanging the O/S while your application is running and the user want's to

Rate Let your application close orderly before the system reboot. Avoid hanging the O/S while your appli

• 1
• 2
• 3
• 4
• 5

(1(1 Vote))

If you don't shutdown properly your application may not release system resources and the O/S will not shutdown. Users will have to use Ctrl-Alt-Del to zap your application.

Method 1: Create a sub class that will monitor the system level messages from the O/S. Trap the shutdown message and close all database connections and open file handles. I.O.W. do a proper app close and exit. If you have worked with sub-classes you will know this is a very very big pain in a place you do not want pain.

Method 2: The simple but effective method. Create hidden form, which will be your startup object. In the load event of this form you call Sub Main(). In the unload or terminate event (you pic one) of this form you call a shutdown procedure that will orderly close all connections, open file handles etc etc. The O/S sends a shutdown message to the application's main form when it is about to reboot, which will trigger the form's unload/temrinate events. The few milliseconds between that and the actual attempted zapping of your application by the O/S is enough time to orderly close everything.

The NT shutdown command will in fact give a 30second grace period after the message before it will zap the application. Windows 9X will wait indefinately if it cannot close your application.