>>>Greetings!
>>>
>>>I currently use VFP3 and have not yet upgraded to VFP5. As I understand, VFP5 creates only 32-bit EXEs, which would not run on WIN31--however, I think it would need win32s support(?). I need to ensure that my completed applications will be able to run on a 386 Win31 machine. Therefore, do I need to stick with VFP3, or can I use VFP5 to create applications for a 16-bit system?
>>>
>>>Thank you!
>>>
>>>Michael Reynolds
>>>Seattle, WA
>>
>>VFP5 will not work for Win3.11, so use VFP3.
>
>Thank you very much for your reply! So, it appears that the only way I can write code to run on 16- and 32-bit platforms is to use VFP3. And, I suppose that VFP3 cannot compile VFP5 objects. Therefore, how does one take advantage of the power and features of VFP5 if the client needs to use it on older platforms, too? The trend is so much focus on VFP5, and I guess that these people are mainly writing 32-bit apps. I wouldn't want to write an app in VFP5 only to find out later that the client decided they want it to also run on 16-bit platforms. I guess my question is: Unless I stop supporting 16-bit platforms, is it necessary to maintain two different versions of FoxPro? In MS Word, for example, once you upgrade, there's no real reason to keep the older version installed.
>
>Thank you!
>
>Michael Reynolds
>Seattle, WA

If you still support Win3.11 then you develop in VFP3, once you upgrade to Win95, convert your projects to VFP5 (it's very easy) or still run existing VFP3 app, and start new development in VFP5 only. BTW, there are no serious differences between VFP5 and 3.