| Database Cursors - Microsoft Access and ADO | HomePage | |||
| Powered by Webelink.com | # | Cursor | Value | Class | Description |
| 1. | adOpenForwardOnly | 0 | MS Access and ADO | This cursor is a server-side uni-directional only and is also the default cursor for a recordset. This cursor uses the least amount of overhead and provides the best performance using the minimum of system resources. You can only use commands which move through the recordset from the first record to the last record. You cannot issue any commands to backup in the recordset. |
| 2. | adOpenStatic | 3 | MS Access and ADO | This cursor is a client-side static recordset which allows you to move in any direction. This cursor will not show any updates, deletions, or additions to the recordset made by other users, while you are viewing the recordset. This is basically a snapshot of the data at the time it was requested. You can use the full recordset traversal commands, such as MoveFirst, MovePrev, MoveLast, RecordCount, and others. |
| 3. | adOpenDynamic | 2 | MS Access and ADO | This is a dynamic recordset cursor. This cursor will show all additions, changes, and deletions made by other users. You can use the full recordset traversal commands, such as MoveFirst, MovePrev, MoveLast, RecordCount, and others. |
| 4. | adOpenKeySet | 1 | MS Access and ADO | Keyset cursor (keysets are values used to access specific records or rows). This cursor is like the dynamic cursor type, except that you can't see records that other users are adding. Deletions and other modifications made by other users are still visible. This cursor has the highest system overhead of all cursors. keyset cursors are best suited for use with a Recordset in situations where not all the data will be needed at once. |
| 5. | adLockReadOnly | 1 | ADO Cursor Lock Type | The database does not lock records, since you are only accessing them in readonly mode. This is also the default record lock type. |
| 6. | adLockPessimistic | 2 | ADO Cursor Lock Type | The database locks the records being changed as soon as the editing begins. The records are unlocked when all changes are complete. No two users can access the same records at the same time. |
| 7. | adLockOptimistic | 3 | ADO Cursor Lock Type | The database locks the records being changed only when the changes are committed. Two users can access the same record at the same time, and the database must be able to reconcile (or simply reject) any conflicts created by multiple updates. |
| 8. | adLockBatchOptimistic | 4 | ADO Cursor Lock Type | This mode is required for batch updates using client cursors, and is very similar to optimistic record lock type. |
| © Copyright 2003-2010 webelink.com. All Rights Reserved. | Click to Email for Info | Terms of Use | | ||||