I've not seen "erroneous conclusions" for quite a while- and even then only in response to provocation. Let it go!

I see. So you're saying that if challenged, it's OK to be wrong?

Either you're not reading as much as I am, or you're giving out free passes. Or maybe both.

Rarely does a week go by without some general comment about what .NET supposedly "can't do". Those without actual experience with the tool are not in a strong position to process information about .NET, let alone make declarative statements about it.

A while back a statement was made that the Winforms datagrid was much slower than the VFP datagrid - when challenged, the "proof" was nothing more than an appeal to authority. And an irrelevant one. In this instance, some website KB that discussed the datagrid....and the use of paging. Sadly, the person didn't recognize that the context was the webform grid, not the Winform grid.

Do you see what I'm getting at, JR?????


Do you mean capability or technique? IMHO VFP developers are well aware that you can create data entry forms in .NET.

How many people are aware that you can now filter out duplicate data? Over a year ago, someone complained on this forum (I don't recall who) about the amount of code it took to filter out duplicate rows. You can now do that in ADO.NET 2.0.

That's just one example - I'm talking about capabilities in the tool. I will not say that .NET is as strong as VFP when it comes to local data handling. But it does far more than some would lead a newbie to believe.

Kevin