I'd tend to make the recordset LockBatchOptimistic.

You can then perform Update operations on the recordset as normal, and the 
recordset will behave nicely.

All you are then doing is leaving off the final reconnect and BatchUpdate 
that would normally write the changes back.

My reason for doing it this way (rather than not batched) are that the 
recordset's EditMode and fields' OriginalValue properties are not reset 
after the individual Update operations, giving you a better degree of 
management over what has been updated and how - particularly with 
reference to the ability to use adFilterPendingRecords and 
adFilterAffectedRecords.   


## dave ##

> 
> Hi,
> 
> If we have a disconnected recordset with a client side cursor. Is the
> recordset updateable?
> 
> The purpose here is to use the recordset as a datastucture which the 
program
> can manipulate. The changes in recordset will not write back to the
> database.
> 
> Thanks,
> 
> Mark
>