With my luck, I'll be responding to a post stating that VFP can turn cattle into airplanes

With my luck, in your next post you'll be demanding that I justify the above. ;-)

I haven't "seized" one word.

Of course you have. you've posted a huge analysis of the word "contributed" implying it means the opposite of what I actually said.

My point is that there are many things that can be done in ADO.NET, just "differently" than VFP.

Now who can disagree with a truism like that? ;-) You can do most things in ADO.NET- actually ADO.NET does quite a lot of things far better than VFP. Data isn't one of them. MS has said it intends to address the deficiency.

The end result is often equal or comparable enough. Good developers learn how to solve those problems and move on.

Some might find that last sentence provocative. ;-) Fact: dotNET's difficulty with local datasets can only be overcome by not using them. "Good developers" who understand reasons for large local datasets may not be satisfied with that. We should also be able to say so without facing taunts and abuse. Perhaps you should review that particular discussion, because your recollection seems to be different from mine.

there's no question that ADO.NET's capabilities have been superficially assessed.

Perhaps. But two wrongs don't make a right.