>I have a few questions for you:
>
>[1] Is there an effort within MS to encourage VFP developers to learn .NET with hopes that, one day, VFP development will cease. A simple YES or NO answer is required here.
>
>[2] If YES is answered above, then the question is why? Please don't say that MS does not have the resources to continue VFP development - that answer is unacceptable.
>
>[3] Is it true that .NET development is not being embraced by development communities as planned? Is this the reason for [1] above?
>
>[4] Can you honestly say that the costs associated with developing a database application with VB.NET will be comparable to the costs developing the same application with VFP?
>
>I hope that you will not dance around these questions, but give us some straight forward answers.

I'm not going to answer these questions directly. I will say that while we continue to enhance VFP, we are adding more and more resources to VS/.NET and that includes adding VFP like features to .NET including data-language and other things found in VFP. The main thing we encourage to VFP developers to do besides upgrading to the latest version (9.0) is to consider using .NET with VFP when it is applicable, like ASP.NET with VFP. It is possible that long term, using and adopting .NET is in your best interest, but that is up to you decide if and when. Even though we are enhancing VFP beyond 9.0, remember that VFP 9.0 is supported through the end of 2014. There are many developers using FoxPro 2.x and VFP 6.0 today, even though they are no longer supported.