I've used VFP for Datacentric apps for 15 years utilizing it's available features: SPTs, RVs, and CursorAdapter which are good but it doesn't mean today that these are better than LINQ, Dynamic SQLs, nHibernate, and the latest from MS - Entity Framework 4.0 which hopefully is matured enough to handle data which will be made available in VS2010.

I think we may be at cross-purposes. IMHO NET has been OK at DML ever since the typed dataset- we've had some quite good threads here comparing typed datsets to L2SQL in which I suggested that the typed dataset is better because it carries change tracking between layers. In 2010 IMHO there is nothing particularly special about getting data in and out of backends or packaging it for display and I don't believe that anybody is saying that VFP's methods are somehow superior at loading/saving remote data, though I still quite like the RV ;-) I think when people talk about reasons for continuing to use VFP they're talking about a lot more than DML. In my case I need to process large quantities of data, some of which needs to persist. As it happens,VFP is rather good at that.

In my opinion, .Net tools evolved that far. It is so far that VFPers might be left behind farther than how they think it is if they will not act today.

OK, but I've been involved in investigations of NET for data processing since 2002 and actually moved away from VFP (to Java, in the 1990s) for some of the reasons you describe. Still I consider that VFP has its uses though I agree with you that the UI side can be written easily enough in NET- or any other contemporary tool for that matter.

BTW, do you use L2SQL? If so, I assume you're aware of all this: http://www.thinqlinq.com/Post.aspx/Title/LINQ-to-SQL-enhancements-for-2010