>>We are trying to theorize how to employ a class in an application that when attached to an open form will 'log' the user off if there has been no activity within a stated time period and would orderly close transactions, forms and the application itself.
>>
>>Has anyone done one of these? I did see an application called 'Seizeapp' but all that did was send a screen to the users notifying them that the server was taking them down.
>>
>>Thanks for the info.
>
>If you want it to clse gracefully, saving changes and closing transactions, you need to give each of the forms in your app a method that can be called at any time to perform this, and keep this in mind when designing each of your forms.
>
>Say you decide to call this method SaveAndClose.
>
>You might then have an application level timer that checks for activity according to whatever you deem is "activity" after so many minutes of inactivity, the timer loops throug all open forms and calls their "saveAndClose" methods, and then calls the function that shuts down the application.
>
>The key idea is, this doesn't come for free. You have to design your application so that a generic process has the power to put it to sleep gracefully, and not in a haze of errors.

---

I agree, if you goto some software site such as www.softseek.com
you may find some scheduling program even shutdown window at certain time!!

what you need to add is:

On ShutDown do SaveAndQuit.prg

and it call all forms to do SaveAndClose...
Ask the application to close is easy, use timer to check time but as Erik said,
to ensure all data is Committed or skip save before quit is more important!!