A cursor model for clients that work with cursors but don't hold locks on the server or issue updates by row. Instead, the client updates many rows that are buffered locally, and then it issues a batch update. This cursor model also allows the client to drop the connection to the server and re-establish it with the same server or even a different server.
To use batch updating in DAO 3.5, you must use an ODBCDirect workspace, the DefaultCursorDriver property must be set to dbUseClientBatchCursor at the time the Connection is opened, and the Recordset must be opened with the OpenRecordset method's locktype argument set to dbOptimisticBatch.