The VFP community said don't move it because we were told, accurately at the time, that VFP would lose many/most of the features that we like about VFP if it were moved (somewhere in my email archives I have that same message conveyed to me by the prior two VFP product managers). Conditions have changed; MS's decision has not.
>
>
>When this first came up, it was the developer community that begged MS not to move VFP to dotnet, and my understanding is that it mostly was because it would likely have entailed theloss of the data capabilities of native vfp. VFP would have had to move from the current data system to ado.net, and nobody wanted that.
>
>>