I do mine much the same way except without the table of the name of the current version. I just have my launcher app (I call it 'stubby' ... don't ask) look at the version info of both server and client version and then copy the newer version from the server if need be. If I have to downgrade the clients to an older version (it's saved on the server just like you describe below Cindy) then the 'stubby' has a list of available versions still on the server that they can use if appropriate to their version of database(s).

Best part about it is that I can maintain all of the versions (removing the old and adding the new) from anywhere I have an internet connection. Simply go to their webserver, connect with their VFP COM object sitting there for web-stuff and tell it what to do, tell the users to just shutdown their app and restart it. Database changes are trickier but can be handled too.


- A Hilton



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