>>
>They have taken forward some for .NET. Are they not taking it forward anymore in the future?
>>
>
>I am sure they will continue to innovate .Net. Not sure what this has to do with VFP...
>

Ugh. Fingers not working well today. Should read
"They have taken VFP forward some for .NET. ..."
So, is MS not taking VFP forward anymore in the future?


><<
>I can certainly understand not going forward with integrating VFP into .NET in this (or the next couple) release(s) for this reason. The entire structure of VFP would have to change.
><<
>
>Again, you reached the right conclusion, but for the reasons. The app and data models in .Net are counter to VFP's. To force VFP into that space would make it almost identical to VB. Well, VB already exists. There is no room for VFP in the .Net space...

Gotcha.
Thanks for the clarification.