Hi Barbara
Here, it is a managment issue.
I used this method before on other application and I propably need to investigated again and try to convince the management about copying exe to hard drive.
Thanks
Mo
>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.
>
>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
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only