>Mo,
>Why not use a 'wrapper' program which copies the EXE to the user's hard disk. Two benefits: First, the EXE on the network isn't opened by anyone so it can be replaced easily. Second, the EXE loads faster if it's on the user's C drive. You can write the wrapper so it compares file date/time to see if it should update the user's copy. We've used this successfully on a large app for over 2 years, and I know other UT people have their own versions.
>

That's fine advice Barbara, except that with potential variance in date-time stampig, it's turned out to be unreliable in some circumstances. I've had far better results assigning a new version number to each executable, and then comparing versions use AGETFILEVERSION() from VFP6 - the was a similar FoxTools function in earlier versions; see George Tasker's Extended FoxTools Help, downloadable from here on UT.

>HTH
>Barbara
>
>>Hi all
>>
>>I just deployed "test mode" a small application/one tier on NT to be used heavily by 100 uesrs.
>>
>>I have the EXE on network which I want to update when new changes is ready, so as with all other applications I ask everyone to exit and replace the old exe with the new one. simple procedure.
>>
>>On this application it tell me that it is in use and I can not change it, I went to the network engineer and it shows that some users have hold on it, which is totaly wrong, those users were not using it.
>>
>>Does this ever happen to you??? and why???
>>
>>The application uses teh Calendar activex which is installed locally.
>>
>>Thanks
>>Mo