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.

>>Yeah. Well, I'm no big fan of ADO for these issues and also the fact that
>>it is slow in record level parsing. This is a huge problem for ASP pages
>>which must do this stuff so frequently. This is one big reason why VFP created
>>Web pages are so much faster.
>
>I definately go VFP COM for any data processing requirements with ASP. I tend to stick with ASP and ADO where simple SQL's will do the job (unless the amount of data being returned to the client warrants going COM). Most of our intranet pages are hit infrequently but require substancial data processing. We do not have a high volume of server requests, typically 5 to 6 hundred a day so some of the speed issues you are concerned with (especially for high volume sites) are not an issue for me.
>
>>ADO has an export mechanism via the save method, but it's a proprietary format.
>>What would work if somebody had thought about this is that one could do the
>>import from the save file into a VFP cursor.
>>
>>I haven't looked at the file, but maybe it's something that can be used with
>>VFP or parsed at least.
>
>I wasn't aware of a save method???!!! I'm looking at the latest ADO doc and I see no mention of it, of course I'm still on my first cup of coffee. Please point me to some info on this. It might provide a solution. I have no problems writing a parser in Vc or assembly if the end result is faster conversion.
>
>>VBScript classes are pretty limited. They must reside in the same module
>>that they're called in, so these classes cannot be reused. It's a good
>>idea though to organize logic away from the bulk of the HTML text.
>
>Very limited, but hey we are talking VBscript here :).
>At least a client can make calls to multiple classes as long as each class resides in a seperate file. This does allow for grouping of like functions. I really like having the ability to do server side processing via client requests without issuing a http get or post (or writing java applets). This fills a void with DHTML especially dealing with data validation issues.