Thom
Nov 22nd, 2000, 04:31 PM
HOW do we duplicate DAO’s Recordset Table-locking in ADO?
What I want to happen is when an admin pulls a disconnected recordset from a Table in the A2K database, the underlying table the recordset was pulled from is LOCKED until the admin is done & Updates his changes back to the Table(using UPDATE SQL statement for the changes).
I was told in this forum that ADO doesn’t support pessimistic locking for client-side cursors; so how in the *$%(#*$# are we supposed to DO this with ADO? Anybody have a clue. I thought about using a connection with the MODE property-but Mode doesn’t work on client-side cursors either! Help!! How is everyone else ensuring that their Databases are locked while Updating/Inserting new info?
What I want to happen is when an admin pulls a disconnected recordset from a Table in the A2K database, the underlying table the recordset was pulled from is LOCKED until the admin is done & Updates his changes back to the Table(using UPDATE SQL statement for the changes).
I was told in this forum that ADO doesn’t support pessimistic locking for client-side cursors; so how in the *$%(#*$# are we supposed to DO this with ADO? Anybody have a clue. I thought about using a connection with the MODE property-but Mode doesn’t work on client-side cursors either! Help!! How is everyone else ensuring that their Databases are locked while Updating/Inserting new info?