<snip>
>But this is not about you or I debating pros and cons. Microsoft has it's own battle. And it's not about VB or VB.NET versus VFP. It's about proprietary versus open-source. Inside Microsoft, VB versus VFP is a non-issue. That decision has already been made. Our liking it, or not, doesn't matter.
>
>We're sitting in limbo waiting for Ken to give us some clues as to what's ahead for VFP. I'm dying to know, just like everyone else.
>
>It won't be long now...
>

Hello Guy. Thanks for your post but I am not debating VFP vs. anything. I am also not trying to promote a VFP.Net. I am pointing out that users of VS.Net apparently would like more "VFP-like data features". But instead of porting VFP to .Net MS have chosen to rather implement new features into the .Net languages. In the meantime other dev tool vendors are moving their tools to .Net so clearly this is possible. For God's sake we have Cobol.net. And just look at what PCSoft have done with a tool which is very much like VFP complete with native database system not based on ADO.

Anyway, it's a dead horse and I argue more against the reasons given rather than the actual merits of a convertion. iac, I have been properly put in my place in another post so I dont have the interest to pursue it further. I leave that to DenisC :)