> If order to create a VFP .NET language, you would lose the VFP data-centric commands and functions since .NET languages are built around ADO.NET and other .NET Framework classes, you would lose the native database engine since that is not part of .NET

>We have decided that what customers want and need is VFP like feature added to the Visual Studio shell, .NET languages, and .NET Framework.

Ken,

I'm sorry, but this does not make any sense. If you look at the two statements above in comparison, what you are really saying is:

1 - VFP cannot be made a .NET because certain parts that are in VFP are not in the .NET framework/shell/whatever

2 - You (MS) want to add those parts to the framework.

Now, this means that it is, of course, entirely possible to build a VFP.NET with all the features that make VFP such a strong product, you have just chosen not to.

Eyvind.