Steve,

This is not clear for me. First, OLEDBFox should work faster than VFPCOM.
Next, you wrote about GetRows() and 32 fields limit. But OLEDBFox doesn't use ADO at all and GetRows() in particular. All it makes with ADO recordset is getting of OLEDB IRowset interface.
GetRows() used in jcRsToCursor program, written by J.Crescencio Flores. As the fastest solution in RsToCursor clone, it was included into my sample for comparison. Sorry, it's not specially mentioned somewhere, but I think that this program is well-known itself (at least on UT).
Last, time ratio 209 secs/57 sec is very similar to jcRsToCursor/VFPCOM ratio. So I may suppose that you have tested not OLEDBFox but jcRsToCursor.

If it's not correct, then you could try to increase speed of OLEDBFox by the next ways:
1. Try the latest version of library. The previous versions has memory leaks, that may lead to loss of performance.
2. Try to retrieve data directly into VFP cursor without using of ADO recordset. It should work with at least the same speed as ODBC connection:

ox = CreateObject("OLEDBFox.Connection")
IF ox.StringOpen("Provider=SQLOLEDB;Initial Catalog=northwind;UID=sa;")
ox.Execute("SELECT * FROM orders", "mycursor")
ox.Close()
ENDIF

3. If you have to have an ADO recordset, try to set

CursorLocation = 2 && adUseServer

Alexander

>Oh yeah, and it did > 32 columns that I was having problems with before also.
>
>>The new VFPCOM utility works very well in my early (this AM) runs. 500K record set created in a reasonable 51 secs and the conversion to a VFP cursor took 57 secs. I did not have any translation problems as was indicated in another post regarding this tool this AM.
>>>>>>
>>>>>>>I've downloaded both utilities here at UT and have each of them up and running. Retrieval time of SQL-Server data and creation of a RecordSet is very reasonable but the conversion time to a VFP cursor is SLOOOOOWWW. I'm looking for a possible jumpstart on converting recordsets to a VFP cursor that would be much, much faster. Any thoughts?
>>>>>>
>>>>>>What is "both" ? Does it mean that file #10002 is SLOOOOOWWW?
>>>>>
>>>>>Yes, both utilities here were downloaded including 1545 which I believe you submitted. I'm talking very large recordsets as we have a VFP app and a data warehouse for a database. My test set was 500K records to retrieve into a 32 field cursor. This was using SQL-Server on a 450 Mhz server and a 1.4 Gig Athlon client. 42 seconds to create the recordset...but a whopping 209 seconds to translate to a VFP cursor.