Hmmm... I'm not positive what type of structure it uses. The best I can give you is that the ADO cursor engine is based in a large part of the VFP cursor engine.

I would suggest asking John Peterson as he's the most qualified person I can think of to answer your question.

>>Michael, the answer to your question regarding the Save() method is:
>>
>>Assuming you have a valid ADO connection object, is you set your CursorLocation property of your recordset object to 3 for Client-Side, you can issue the following command:
>>
>>oRS.Save("c:\foo.rs")
>>
>>This will create a "persisted" recordset on your local hard drive. However, if the file already exists, you must delete it first before you can save to it again.
>
>Thanks,
>
>I got the save to work. Dumps the data to file fast alright. Sure would like to find some info on the data structure it dumps to help with the parser. This looks like an approach that may work out for large datasets.
>
>Regards,
>Mike