>Hilmar,
>
>Thanks for the info. Your last statement is the one I am concerned about. Instead of a file I look for a table field value. I will try the file approach. My trouble is the timer that I have firing seems to stop or go to sleep on some machines. When I run my shut down procedure there are always 4 or 5 out of 40 that can't tell the shut down flag is set. Any ideas on this?

Well, simply checking for a file seems a little easier to program; it might be faster, too. But a value in a table might work just as well.

While I didn't have trouble with this, there is a timer from www.bbcontrols.com (free, or cheap) which is supposed to solve some problems with the VFP Timer - including the fact that the VFP Timer doesn't fire when VFP is busy with some long operation.

The thing that worried me, in my procedure, was the following. Invoking goApp.OnQuit() is equivalent to the user pressing Alt-F4 (or selecting File | Quit). If the user has pending changes in some form, this form will show the user a MessageBox(), asking whether he wants to save changes (Yes / No / Cancel). Thus, the application will NOT immediately quit in this case.

While this worried me, it usually didn't turn out to be a problem in practice.

Anyway, to solve this kind of problems, I kept a log of login and logout activity, which would allow me to check which users recently did a login, but no corresponding logout.

Note that the solution I outlined would also allow me to "kick out" the users during the daytime - which we did, though unfrequently, for some change to the table structure that couldn't wait until the next midnight, or for a reindex, in case of suspected corruption.