I don't see the relevance to the question.

I'll assume from your avoiding the question that you haven't developed anything in it.

It is absolutely relevant. Here's why:

I refer to people who have experience with both.

If you have not developed anything in .NET, if you are not going through the learning curve, that puts you at a tremendous disadvantage to be able to process information regarding the topic. The longer you are locked into the Fox way of doing things, the longer it may take you to learn .NET.

For instance, a while back we had a discussion about datagrid performance in FoxPro vs .NET. You referred to information from a site on datagrid performance to prove that the .NET datagrid had performance issues. That site explicitly referred to paging, not realizing that paging is a technique for the Webforms datagrid (a totally different animal). That wasn't relevant to the discussion, as I had previously established a comparison between FoxPro grid vs Winforms datagrid. You also previously misunderstood other aspects of ADO.NET and forms inheritance. Now...everybody makes mistakes - but there seems to be a pattern of making conclusions from an untenable position.

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

You cannot tell me that the LINQ project does not interest you. It has major advantages if they do this right. LINQ will become the next hot-item in .NET and at the same point it will prove the critisism we had for years. So, please spare me your tactics about arguments of blind 'zombie' experience in .NET. Many programmers are just bricklayers who do not have any clue about architectual designs. It would suit you better to admit that my critisism on data integration in .NET was a founded one, now that MS themselves has proven it.

Of course, LINQ interests me. Yes, it provides many benefits. And it also proves MS' committment to continually enhance .NET.

I never said that you could do EVERYTHING in ADO.NET that exists in VFP. All I've said is that in some instances, one can develop functional equivalents...sometimes with a few lines of code, and sometimes with more code that can be abstracted out as a separate class.

What I am saying is that a number of solutions have been developed by myself and many many others, and we've moved on to different things. It's my opinion that some aspects of .NET (including ADO.NET) are understated in the Fox community, partly because there's not a simple 1-1 correlation. Raising one hands in the air and stating they're not going to start working with it until it satisfies all their needs is only denying yourself the learning curve you must go through when learning .NET.

Kevin