>A VFP .Net would simply be VB .Net.
I Agree but why not move VFP towards being CLR compliant.

>All data access would be through XML or ADO .Net.
Why? Are you saying that VFP's native data engine could not be ported to code that is CLR compliant? How about the entire VFP runtime for that matter.

>VFP 7.0 can participate in .Net now by creating and consuming Web Services.
Yes but that doesn't even begin to compare with the ability to drop a class right into a .NET project. If I need VFP capabilities from within .NET today I would be forced to use a COM wrapper. In a year or two does the term legacy come to mind.