>>I have a problem updating or making changes to an app when some user has it open. Some users open the app and leave it running all day regardless if they use it or not. Is there a way to capture their ip or name on the network? The server is not mine and I do not have rights to kick them off. The phone is my way of informing them. Also can I institute some global timeout of nonuse that would exit the app automatically? Wondering.....
>
>Many of us have a small VFP EXE that launches the app. Part of the code in the EXE is to look in a specific subdirectory on the server for a new version of the APP. If there is a new one, the EXE copies it the application install directory. Then runs it. That way I do not have to be there, chase down rogue users, go back to workstations to do re-installs, etc. All I have to do is copy the new APP to the server directory.

Another relatively elegant solution would be to have tha launcher app read the exact name and location of the sub-app from a table or an .ini file. Then you could copy the new app with a slightly different name, and simply register its name in the table or .ini. The chances of collision during the install are minimal - it's that someone may be trying to read the same record from the same table while we're editing it. Yes, it's possible that there will be two versions of the same app running at the same time, but then they're supposed to be compatible, being written by the same author :)