Hi Perry...

While disconnected have the necessary schema info to allow updates, they cannot update because their physical link, the connection object itself, is not present. A recordset has an ActiveConnection property. On a disconnected recordset, this property is Null. Check out my whitepaper on this....

So, to have a disconnected recordset capable of updates, simply instance a connection object, provide the connection object with the neccessary data to open the connection, and invoke code like this:

oRecordset.ActiveConnection = oConnection

Once again, check out my ADO whitepaper for all the grusome details!!! <bg>..


>Quick question (or 2) for my understanding.
>
>Does disconnected recordset mean there is no link back to the originating data source? Does this mean this functionality is limited to reporting or is there a way to update the source data with a disconnected Recordset?
>
>TIA,
>
>PF
>
>>With respect to ADO, I am not sure there the two calls come in. Bascially, I can invoke a method that returns a disconnected Recordset. Sure, I have to query the interface, invoke methods and such. But, I need to do the same thing with XML parser.