>>>>>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.
>>>
>>>Is this install dir on the server?
>>
>>The EXE and APP reside in the [local] install directory. The directory where I put the new version of the APP is on the server usually in the directory of the data:

>>
>>f:\apps\myapp
>>f:\apps\myapp\data      && data directory
>>f:\apps\myapp\reports
>>f:\apps\myapp\appupdt   && new version of APP and whatever else needs
>>                        && to be copied to the app install directory
>>

>
>TO TEST FOR NEWER VERSION, are you using the fdate function? Or how do you test?

I use the ADIR() function twice, once on the local drive and once on the server drive. I then compare the dates of the 2 files. If the local file is older than the server file, I set a flag, llNewVer = .T. If the dates are the same, I check the time of each file. If the time of the local file is earlier than the server, the llNewVer is set to .T. Then if llNewVer = .T. I copy the server file to the local directory.