>>>You should experience no problems upgrading from VFP5 to VFP6.
>>>
>>>VFP5 and VFP6 can run at the same time on the same machine.
>>>
>>>I don't understand your third question because deployment and building an executable are two different things. But, building an exe in VFP6 is the same as in VFP5.
>>>
>>>Dave
>>>
>>
>>Dave, the only amendment I'd make to your statement is that whichever VFP is installed last is the one that ends up owning the VersionIndependent ProgIDs for VFP file types, which can cause some confusion when both VFP5 and VFP6 are installed. If you want VFP5 to launch by default when you double-click a .VCX in Explorer rather than VFP6, install VFP6 first, and then install VFP5. Last man standing wins...
>
>You are correct, but I'm curious to know why you would you want VFP5 to be the default version launched if you've upgraded to VFP6.
>

I didn't, but I ran into a client who had a mix of VFP5 and VFP6 apps in transition; he needed to make sure that his stored procedures in his .DBC compiled under VFP5 and not under VFP6; VFP6's p-code parser apparently can work with VFP5-compiled p-code, but not the other way around. I ended up having to help him dink around a bit to make sure that when he made mods to his .DBC, VFP5 fired up rather than VFP6. The easiest thing to do was to redirect the shell open command linkage in HKCR for the .DBC file extension to launch VFP5; not a big deal, but it did cause some confusion, and does pose a problem if you're using SPs in a DBC and they have to work under both versions.

>If you did want to launch VFP5 from accessing VFP files in the Explorer after a VFP6 install, you can add VFP5 to the "Send To" menu and right click the file instead of double clicking.
>
>Dave