>>>>>Hello Rob!
>>>>>
>>>>>I'm not agree with your statement about MS position. I think that Win 3.1
>>>>>will never die because the customers spend already so much $$$ to Win
>>>>>software. And I think that VFP 5.0 is a better database development tool
>>>>>ever created on the Earth... ;)
>>>>>
>>>>>Have a happy day
>>>>>Vladimir Shevchenko
>>>>>
>>>>>> win95 and do whatever, but vfp50 and vfp50 apps can only run in win95? I
>>>>>> guess
>>>>>> MS has decided that all the users of win31 will change to win95 soon..
>>>>>>
>>>>
>>>>hi Vladimir: If win31 is here to stay, why does vfp50 only work in win95?
>>>>I agree with you. I think that vfp50 should work in win31 and win95.
>>>
>>>You have vfp3 for this purpose. Note that it's extremely difficult (and dangerous for product reputation) to preserve all backward compatibility. I assume that some 'specialists' making product evaluation in magazines just open VFP manual, see some oldest-style command like INPUT, and make conclusion this is still xbase crutched veteran.
>>
>>thanks Edward for your answer... my point was... why do I have to code in
>>two programs (vfp30 and vfp50) to get my app to work in win31 and win95 if
>>I want to code in vfp50. Vfp50 should work for both win31 and win 95 until win31 is gone. ..and.. what I am saying, is... MS is pushing out win31 and it is obvious... do you agree or not?
>
>May be, MS selected personally you to push? Other people do VFP5.0 for strictly Win95, and VFP3.0 for 'broader' base. Don't worry about VFP3 obstacles, it's almost 100% similar to 5.0, except some advanced topics.

If MS selected me to push VFP50 and paid me, I would.. I guess I was just wanting the latest tool (vfp50) to handle the broader base... I view vfp50 as
an upgrade to vfp30 and not different package that works on a newer platform...