>My main point is that people who are intimate with VFP will naturally ask for a .NET version rather than simply accept that the have to LEARN another language. Is it so hard to grasp that people who worked hard 'getting' the subtleties of VFP don't want to spend an even greater amount of time learning the same for yet more languages and facilities???? Is it that hard to grasp that people do not want to be in the 'minimally capable' category for expertise in a language for years to come?

When folks are made aware of the sacrifices involved (which have been iterated here and elsewhere numerous times), from what I gather most say they don't want a VFP .NET. As JVP has pointed out, take away the VFP data engine (which you'll have to do to have a .NET version), and you've basically got VB .NET. Any subtleties of VFP are more than likely going to disappear when it compiles to the CLR.

We already went through this argument last year, so I'm done beating this long-dead horse.