Remember the potential collision problem. An ADO disconnected recordset does
three things on reconnect/updatebatch

1. Determined which records/ fields have changed via the ADO's New and Old
values
2. Verifies the Old ADO values match those in the DB - If someone has modified
a record since your ADO rs was disconnected from the DB, ADO will not allow
updates.
3. The update occurs to the fields changed.




"Tom Shreve" <toms@wakely.com> wrote:
>One possible gotcha - my memory is fuzzy, but I don't think the UpdateBatch
>method works if you add records to the recordset.
>
>>After the recordset is modified, you have to re-attach it to the connection
>>object (Set myRs.ActiveConnection = myCnn). After the rs has an active
>>connection, execute the UpdateBatch method.

>
>
>