Arthur,

Nick's launcher (download #9668) solves the problem of updating an .exe on the network. Each user gets the new copy of the executable copied to their local drive the next time they enter the application.

Of course that doesn't solve your problem when you want to get users out of the system for other reasons...

>I'm a nice guy. I really am. Invariably, however, one runs across a situation where, in order to please one person, you have to rebuild an executable that yet a third person has open. Maybe this third person has gone to the rest room, maybe to lunch, but no one has seen them today, and their screen saver is on and I really don't want to just shut off their computer for fear of some file getting trashed. OK, I'm not a nice guy ... I don't turn off the computer because *I* would have to fix any files that might get trashed.
>
>So I'm playing the Grinch.
>
>I'm contemplating ways to shutting down Foxpro applications either on demand over the network or after a period of inactivity. I thought about writing an FLL to capture null events, but null events occur all the time and anything constantly capturing them would be *almost* as bad as the proverbial "tight loop."
>
>Does anyone have any suggestions for terminating programs that have been left running?