Hi!

You can make a 'brother' service that will run together with the main application and control seizing. When application does not shutdown during 10 minutes after seize launched, brother service uses API functions to kill a process of main application causing it shutdown without any messages. This might cause, however, data loss if user left application in teh data editing state. I can make a sample for you if needed.

BTW, the same seizing preventing occurs when user opens dialog boxes like getdir, getfile or getcolor and leave them in the opened state.

>My company presnetly uses the seizeapp routine from up here in the libraries..I have a question about problems we are having with its usage..
>
>There is one major flaw in the routine, that does not kick people out of the application.. If a person has a print preview or report printing, the application does not respect the seizeapp routine. Also when an application is minimized the same thing happens.
>
>Is there a way to have this work in reports and when an application is minimized?
>
>Thanks!