>> I was suggesting that M$ go the other way: incorporate VFP's functionality into it's .NET family of languages. <<

What is in VFP that isn't already in .NET? It has the ability to access a range of data stores via ADO.NET. It has the ability to create forms (including web forms) and menus with GUI tools. Etc. I don't know what such an incorporation would bring to the table other than making the migration easier for VFP developers. And I think we all know how likely it is that Microsoft will do it for that reason.

Mike