>>Thanks for the link. I'm already using (rather, learning) ADO with SQL OLEDB provider. I'm in the process of exploring my other options for getting to SQL Server data. It seems that remote views and SQL pass-through are mentioned more often around here than ADO, so I am checking those 2 routes out.
>>
>>As far as I can tell, you have to use an ODBC connection (not OLEDB provider) to use RV or SPT.
>
>ADO is the standard mechanism for talking to an OLEDB provider. I don't know of any tools (I'm sure there are a few) that communicate directly with the OLEDB provider, probably because MDAC is changing all of the time. In general, if you want to work with a VFP cursor, RV or SPT through an ODBC connection works best. If you need to pass data as an object across COM boundaries, then ADO is probably a better solution. I have not had a lot of success converting ADO Recordsets to VFP cursors (and vice-versa). COMCodeBook (www.comcodebook.com) and other frameworks probably help a lot in this regard.
>

Joel,

ADO seems to be very flexible, but cursors are nice, too. I haven't spend much time on the recordset to cursor conversion problem. It seems possible (with certain limitations), but it is certainly a hurdle.

Thanks for the synopsis,