I appreciate all this information. Thanks. Can you explain the significance of using adUseClient instead of adUseServer with respect to performance?

>As long as you have a static type cursor this routine will not run into the VFP array limitation. If you have a large recordset it will still take its time but not much more compared to VFPCOM.
>
>If the cursor type you retrieve does not support bookmarks (see the class) then this code may fail depending on how large the rs is.
>
>Just set a cursorlocation of adUseClient and a cursortype of adOpenStatic when retrieving your recordset and you should be fine.
>
>Also note that this conversion class does not support binary fields. (images and such)
>
>>Thanks - that's pretty much what i was looking for. One question though, since the RecordSet.GetRows() method dumps the contents of the recordset into an array are there any concerns (either physical limitations of VFP or severe performance problems) in the case of an RS with lots of rows and lots of columns? If so, would it be better to process each record set individually, that is, loop through the record set and insert one at a time into the cursor?
>>
>>
>>>>Hi there.
>>>>I am using ADO to generate a record set of data from SQL Server. Then, I convert the record set to a foxpro cursor using the RStoCursor method of VFPCom.ComUtil. This works great, until.... I then built my project into a multi-threaded com server. When I used my com server, it crashed - took me a while to figure out why. Apparently, the VFPCOM.ComUtil throws up a MessageBox saying "This OCX can only be hosted by Visual Foxpro". I'm guessing that VFPCOM doesn't realize that my com server is visual foxpro.
>>>>
>>>>Anyone have any experience with this or know of a work around (short of sifting thru the RS myself and building my own cursor :)
>>>>
>>>>Thanks!
>>>>Alan
>>>
>>>See http://www.levelextreme.com/wconnect/wc.dll?FournierTransformation~2,54,Forum=5,28,1454 for an alternative. HTH