>For previous versions of VFP, executables could be built in any version and deployed under any runtime version (generally speaking). This enabled us to stagger our library file upgrade - with a couple of hundred desktops, this is a critical issue.
>
>If I gather correctly from various posts, this option is broken under VFP8/VFP8SP1. If so, we will probably never use SP1, as the logistics versus the benefits do not tally.
>
>Does anyone have a definite answer to the question: can an exe be built using VFP8SP1, and deployed to users with the base VFP8 runtimes? Are there situations where the answer changes - ie using certain features such as the cursor adapter?
>
>If the answer is no on any or all counts:
>1. Shame on Microsoft
>2. How do I remove SP1 from my PC, given that there does not appear to be an uninstall option?

A 'Hello world' VFP8 RTM exe will run with the SP1 runtime, and vice versa, in my testing. If the SP1 exe contains new features, (new SET TABLEVALIDATE values, CursorAdaptor PEMs) you will of course get errors under the VFP8 RTM runtime. From a Microsoft support standpoint, mixing .exe and runtime versions is not optimal or encouraged, but should work, as it did in VFP7/VFP7 SP1.