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.

Steve

>>>>Hi!
>>>>
>>>>>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 #1545 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.
>>>
>>>Steve
>>
>>File #9916 works best with static client side cursors. Also try increasing / decreasing the "lnMagic" number in the conversion method to see if that makes a noticeable difference. Still 500K rows is a lot for any data transfer process conversion or not. HTH
>
>Thanks, I'm still working with this stuff. We actually run queries that have result sets much larger than 500K also. We are also evaluating different mechanisms for display of this data in hopes of cutting down the amount of data coming across the wire but that's future and we need to deal with the now.
>
>STeve