Hey great a 3rd way!

>I have a "launcher" app on the server which seldom changes. It opens a free 2.6 table with the name of the current version. A power user can edit this file in Excel in an emergency to go back one version. Then the launcher app calls the current version. I keep a couple of old versions on the server, deleting the oldest one when I create a new one.
>
>The launcher is something like MyApp.exe and the version is something like MyApp17a.exe. The desktop shortcut goes to MyApp.exe.
>
>Solves the problem of getting the users out when I have a new version, and everything stays on the server.
>
>Just one more way to do things!
>
>
>>One other reason to have a startup exe that copies the exe locally is that you can very easily copy and updates to your main exe to the server and it will be automatically distributed to everyone the next time the start the program and you never have to get all users out of the program.