Ahh.. The only other thing I would suggest is Popping a Window Up that
says to the effect: Another Copy is running, Are you sure you want to run
another.

(Also would suggest doing something about the network since it is only
a matter of time before the Tables / Indexes become corrupted due to
people yacking (Technical Term <g>) in and out of the network)

Good Luck!


>I use the same approach with other clients. The problem this client's network is EXTREMELY unstable. Users get kicked out several times a week.
>
>Unless the trigger file (File created on startup of the app) is left open for the entire time the app is running and only closed and deleted on app termination; the second instance of the app cannot tell if the first instance if the app is still running or the app died without deleting the file. Keeping the file open the entire time app is executing and trying to delete the file if it exists when the app starts will prevent the app from running multiple times because the file cannot be deleted.
>
>
>
>>Hi Fred,
>>
>>We usually created a File on the way in, and removed the file on the
>>way out. Upon Entering the Program, we look for IF FILE('FILENAME.TXT')
>>and Cancel if it exists.
>>
>>That way it doesnt matter how many Opens / Closes Exist...
>>
>>HTH!
>>Bob :-)
>>
>>>I have a client with numerous Foxpro 2.6 DOS applications. They want to limit the users to only running one instance of the programs. These engineers will have the same program open 8 or 9 times and wonder why their computer is running slow. I know how to do it in windows and the method I use for DOS won't work.
>>>
>>> Unfortunately, CLOSE ALL is spread throughout the code of all the programs so using a low level file open/create to make a file that only exists during execution of the program won't work. This is the method I've used in the past.
>>>
>>>Help!