>You can use ADO or ODBC. I pefer ODBC because it directly returns a cursor, which when added to the DE can be a subclass of a custom cursor object. This is how to build custom OOP data access frameworks. ADO returns recordsets that need to be exported to cursors to do anything useful. You can not subclass ADO recordsets or bind them directly to VFP controls.
>
>As for SEEK, forget about it! SQL is a primarily set based language and does not really support iterative commands. You can use SQL cursors if you need to work "row by row", but they are not that useful and they recommend you avoid them as much as possible.
>
>Charlie

You can work directly with ADO recordsets just fine. It may be slower than the native VFP cursor, but that doesn't mean they are not useful. They come in very handy in middle-tier MTS-based components. But if convert you must, check out my GetRows() version of RStoCursor routine in the UT downloads :)