This is what I did in Bata/Bolivia:
The first version of the executable was compiled with a name similar to MYAPP_0001.EXE, the next version as MYAPP_0002.EXE, etc.
A small loader program searched for the latest version, and loaded it for the end-user.
A separate version of the loader program (which I eventually combined with the previous one) allowed the user to select from the list of available versions (I kept the last 30 versions), to load a previous version. Very useful if the latest change produced unintended side-effects.
Of course, I could compile and update the executable while users were working - that is why I started this system in the first place.
A Timer object checked for a newer version every 2 minutes. If a newer version was found, the user was informed. It was then up to the user to exit and restart, or continue with the old version.
An HTML file on the shared folder contained a summary of the latest changes.
Database updates usually had to be scheduled for midnight. However, I also had a timer check regularly for the existence of file maintenance.tmp. If the file existed, the OnQuit() method of the application object would be invoked. This was not a fool-proof method; if the user had pending changes, he would be asked whether he wanted to save. If the user went out to lunch, the program would stay in the confirmation MessageBox(). This is the theory; in practice, I always managed to throw the users out when I had to do emergency updates to the database structure.
HTH,
Hilmar.
>Hello everyone,
>
>I am gradually rewriting a huge Foxpro/DOS application in VFP 7.0 while it is actively in use by about 55 users. I have my Installshield setup configured to place the EXE on the local hard drive, and all the data is read from the network drive.
>
>I would like to automate a way to flag the user if there is an update to the version of the EXE on thier local drive, and give them the option to update it immediately.
>
>I'm not sure how an updated version number affects an install/update of an existing program, etc...
>
>I am reading up on using version #s in my exe, but if anyone can point me in the right direction I'd appreciate it.
>
>Thanks in advance,
>Larry Morelli
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
