>>OK, I'm going to have to disagree here based on my little experience with C#. I've started working with these objects and while it is not as native to me as local cursors, they are not a pain in the a$$ as you say. I haven't done any real speed tests to determine if manipulating data via objects is that much more cumbersome, but so far so good. I haven't seen any real degredation. The biggest stumbling block is my inexperience. I have to look everything up and search for examples while I can work with data in VFP practically with my eyes closed because I've been using VFP since the mid 80s. When I want to do something in VFP, I can immediately think (in most cases) of 3-4 ways of accomplishing it. In dotnet, due solely to my inexperience, I have to research how to do it and then test each option to determine which one suits my needs best.
>>
>>
>>
>
>I stand by my statement. I can create a cursor from a SQL Server database in 3 statements or less (including making connection). I can then slice/dice/serve up that cursor into other cursors/arrays/variables/etc with (usually) single statements from then on.
>
>If I can do that in C# with as little effort, then I'll stand corrected.

You can slice/dice/serve up that ado objhect into other adoobjects/arrays/lists/variables/collections with usually single statements form then on.