>Yeah but do your users actually have VFP dev platform installed?? Or just your app? If the users are just running your app, it's not really a "service pack" as far as the users need be concerned. You have to recompile you app and rebuild distrib directories... effectively your generating a new version. If use a formal versioning scheme, all the usual policies are gonna apply everytime you rebuild... so to the users it's just another 'new version'.

True, just a new version, but one without new features.

>What I'm getting at is, I would thinkn if you have launcher progy in place, surely it's got (or needs) a mechanism to handle upgrading to new versions. A rebuild from a new service pack shouldnt really cause any differently handling than want a good upgrade mechanism would do.

The only catch to this is that the VFP runtimes are being updated so I must move the launcher:
FROM:
1) copying the EXE
TO:
1) Copying the exe
2) start an unattended install of the new VFP runtimes
3) reboot

I am not saying that this is particularily difficult, but it requires that the launcher be written in something other that VFP. Preferably something without runtimes. For the simple reason that I won't need to updated the runtimes of the launcher as well (think endless loop). The launcher would also need to detect which type of install needs to be done... just a EXE update or an EXE and VFP runtime update.