>Anyway, the answer is that the program has done an auto-update and must restart to run the latest version.

We used to do that in our VFP programs, but Vista has me too worried about UAC stuff.

We moved the update part into our inno setup program and have no more trouble with Vista.

The only direct solutions we found to the restart after update problem were a separate exe (now you have another program to update - yechh) OR to write a batch file on the fly, execute the bat file, and quit.

I like using inno setup a lot better than the separate exe or the bat file.

We use our inno setup program both for the original install and for program updates.
Inno can pull the files from your web folder, so every time you run it you get the latest version of the files from your web folder.

We have our VFP program check for new files on the web folder at startup.
It only pulls down a list of files and datetimes and sizes - it is a very small download and goes quickly.

If the VFP program detects any new files we ask the user if they want to update.
If yes, then the VFP program just launches the setup program and quits.

We wrote a custom script inside the inno program so that it only pulls new or changed files.
It will not waste time pulling down all the files that are current.
As a bonus, it will also install files that were not in the original install, for instance new reports.

The setup/update program launches my program when it is done.

Let me know if you are interested, let me know.
Perhaps we can turn it into a nice article in the UTMag :)

Best,
Michael