Sorry I meant CursorAdapter. It's one of the most awkward abstraction APIs I've ever seen for doing data access :-) The functionality it provides is decent but the way code has to interact with it is ugly at best IMHO. I never used it beyond playing with it for that reason.

To me the straight forward approach of SQL Passthrough is simply more transparent and allows you full control over the entire data access process...

+++ Rick ---

>Thanks Rick.
>
>In the same spirit, if I may ask, what is wrong with "DataAdapter"? Never used it in VFP, but in .net I do.
>
>
>>The main reason is because OleDb drivers are a pain from VFP. Lots of weird inconsistencies and things that don't work. Plus the only thing that really uses it (with auto-conversion to VFP data) is the DataAdapter which all in itself is oddball funky technology.
>>
>>It used to be there were a few features that only the OleDb provider provided like Unicode transcoding, but that's actually been added in VFP 9 with the Odbc drivers as well.
>>
>>Even if it weren't discontinued I'd stick with ODBC as the more reliable, universally used and overall simple low level technology that just works.
>>
>>+++ Rick ---
>>
>>>HI Craig, why (in a nutshell) is oledb not recommended?
>>>
>>>>No. You have to use ODBC or OLEDB (not recommended)
>>>>
>>>>>Bill: I think that I am the one who is confused. Will VFP7 read a SQL Server table directly??
>>>>>Randy