Walter,

Yes, I had to write some code...that was part of the process of learning C# and .NET. About a year ago I spent part of a week writing a toolkit for data access...I've been a Fox guy since 1988, and wanted to put together a 'library' to do similar data munging in ADO.NET...it was time well spent. I do recall that part of our daily work routine is writing a few lines of code here and there. <g>

Since then, I've had to do some fairly extensive data work in ADO.NET, and really have yet to find myself 'missing' anything that was in VFP.

You say that the approach I posted is 'less efficient' and 'slower'...have you benchmarked them yourself in .NET? Would you care to share the results?

I'll be happy to share mine...I created an unindexed 50,000 row data table, and was able to do random locates in a second or less. Keep in mind that much of ADO and ADO.NET came from cursor technology.

If the situation were reversed...if .NET had some key feature that many felt did not exist in VFP, and someone demonstrated that it could be done in VFP through a custom function with similar outcome...the VFP developer would likely state (and rightly so) that while it took 10 lines of code, it works similarly and won't need to be modified for quite some time. So why is this any different?

As for the OO vs relational, it occured to me after reading your post that we may be talking about two different things. I was thinking more along the lines of classes and common routines for data manipulation. I want to read the thread message that you referenced, so thanks for sending it.

Kevin