There's STILL a problem - odds are there's someone in the module you're trying to update (would be true for many of MY apps, anyway). I have used one solution, and heard of another one that give the best of both worlds...

My solution: by redefining the target of your application shortcut icon, you can direct any NEW users to a different EXE (my_app_new.exe) - without them even knowing about it! I do this with Novell's ZenWorks, but WinNT has such management capabilities as well. Next day, everyone who logged in is now using you new application! To clean up, copy your update to the original filename and point things back to the original filename (my_app.exe, if you wish). Let it simmer one more day, and delete the temporary (my_app_new.exe) update.

(I always set things up so I can manage the applications everyone sees on the network locally, so I don't need to waltz to 90 different machines and interrupt work to do an update or install a new program).

The one I heard/read about: write a front-end (VFP or VB) that looks into your application's directory and runs the most recent version of your progam. Program names can be my_app_001.exe, my_app_002.exe, etc.

Whichever you prefer!

FWIW

>
>You all are right, but, in a network environment is a lot easy
>to maintain an application if it is broken in pieces. I do that,
>let's say that you need to make a change to a function or report,
>right at the moment while users are working , you have to make
>the change, recompile and stop users from working to replace
>the "exe" file, in the other hand, if your function or report
>is a stand alone file, you just need to replace that file,
>and you have a good chance to do it without stoping the users
>from working.
>
>Hope this helps..