>So if I understand correctly MS developed a set of tools (.Net) based on two languages that don't really have data functionality and now you're adding data functionality to it.
>
>Would'nt it have been easier to start with VFP, which already have data functionality and build .Net around it?
>
>I don't know just an idea I'm throwing...

There are 4 .NET languages from Microsoft, VB, C#, C++, and J#. Instead of throwing out ideas, I suggest you spend time learning the .NET architecture (framework, CLR, languages, ADO.NET, .NET languages, etc.). There is no local data engine in .NET, it is all built around the ADO.NET interfaces. In order to add the VFP functionality to .NET, much more has to be added to the .NET framework and languages, not just commands and functions. And in the end, what is best for developers is to get new data functionality in VB and C# rather than yet another .NET language to select from with the same or less functionality as say VB. If you spend more time reading books and actually using .NET, you will be able to start answering your own questions here.