Steven,

I do realize that there are occasions where it is necessary for everyone to be out of your application, but routine updates of your .exe shouldn't be one of them.

In downloads, do a search on "Launcher"...there is one that Nick has out there. It is easy to implement; when you update your .exe on the network your users will get the updated copy the next time they go into your app.

>My app runs on a network. I can shut down the app on any machine by sending a flag to a watched table. When the flag shows up the app terminates. But if my app terminates abnormaly on a machine and is not restarted and shut down properly it leaves it active in the task manager of that machine. When I need to do maintenance on the app and rebuild the exe file I have to have every instance closed. So I have to phyisicaly go to those machines and shut them down. Is there any way around this? Can I break the connection that these two or three out of 40 or 50 users have to the app when this happens?