>>>>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.
>>>


>This is a silly argument - you have to force all users to log out to perform I
I didn't say that you have to logout the users.

the update in any case, and the launcher automates the process of updating - instead of forcing the user to log out and then run an external update routine, then return to his app, all you have to do is update the server copy of the executable, and then have the user exit from his app and restart it, which then triggers the update process automatically.

>
>IOW, the launcher-automated update is a win-win situation - as stations run the launcher, they automatically update the system. Any other way requires manual intervention at each station, rather than a simple phone call or message telling the users to exit from the program and restart the app when the update is ready to run.

Try that with 400 hundred users, I have done it, and allways there
is somebody that doesn't do it.