>I have one VFP 6.0 app with a large install base. The clients are NT power users and I do not want to expend the time to re-install for an update. We have a launcher that performs application updates as required. Since the launcher itself is in VFP it cannot update the runtime's. To install the SP3 runtimes we would have to physically go to each user's machine. Major drag since we just spent three weeks installing the app about a month ago.


Michael, why not have the launcher copy the new runtimes into a work directory.
Then use the runonce registry setting to copy the new runtimes during a reboot.
You could also force a reboot use any of the shutdown api's lying around.


>So now I have two flavors of VFP 6.0 apps to support. It would be nice to be able to do development for both on one machine.


Basically it cant easily be done given that the runtimes are stored in system folder...

However, you could try moving them back to the vfp folder and adding it to your system path.

Also given that SP3 is more than just a runtime update you could be asking for
more problems