>>>I think you better change the runtime files too on the clients side (vfp*.dll)
>>>using older versions may make your app crash
>>
>>I agree. I've gotten away with vfp SP "version incompatibilty" a few times by necessity, and it worked well enough for short periods, but I would never recommend it to anyone, I think it's just looking for trouble.
>>
>>
>>Much easier just to uninstall the SP development upgrades, and do builds with the older version. Unless there is a critical fix, which means a full distributed upgrade anyway.
>
>Thanks, guys - I'll have to make some fixes then. I'll probably add a version check to the launcher, which will then automatically re-run the setup. I guess that would still mean trouble if the actual users don't have the rights to install anything on their local machines.
>
>Seems to be I'm in for a few interesting days...
Additionally, the SPs typically provide more recent versions of ActiveX. When you run the wizard, you may want to reselect for MS 6.0 SP 3 to MS 6.0 SP4 (or SP5) OCX controls.