Excellent reminder! MS has been helping VFP programmers work with other MS technologies since the beginning - one of the benefits of the buyout for VFP developers. They continue to do so today with VFP interop with .NET. There may come a day when it makes sense to make VFP part of .NET and create a clear migration path. Right now I think the most benefit to developers is using the strengths of VFP and combining that with .NET technologies. Why does it have to be an either/or situation? There are millions of lines of VFP code that many companies are in no shape to rewrite and where it would make imminent sense to continue to take advantage of.
>Jess,
>
>>>>>Go directly to the point. VFP started dying. Painful to accept but because VFP is not .Net and it will not be in the future, it will surely die...
>
>Maybe, but Robert Green stated that "FoxPro will exist and continue to be upgraded until the day it is merged along with Visual Basic and Visual C++ into a single environment". (http://www.foxprohistory.org/articles_18.htm)
>
>Don't know if Microsoft plans regarding VFP changed since that...
>
>Fernando