Please help
If I use adlockpessimistic when I open a recordset does SQL lock the record and prevent others to access the record until I update the record?
I have a table with a number in one of its fields. I open a recordset with adlockpessimistic and grab that number then manipulate the number in VB and then takes the new manipulated number and updates the field in the db. My concern is that after I open up the recordset and grab the number another user can also open up the recordset and grab the same number before the first user can update the number. Thus priducing duplicate numbers. Someone please explain exactly what happens when you use adlockpessimistic.
Thank You
If I use adlockpessimistic when I open a recordset does SQL lock the record and prevent others to access the record until I update the record?
I have a table with a number in one of its fields. I open a recordset with adlockpessimistic and grab that number then manipulate the number in VB and then takes the new manipulated number and updates the field in the db. My concern is that after I open up the recordset and grab the number another user can also open up the recordset and grab the same number before the first user can update the number. Thus priducing duplicate numbers. Someone please explain exactly what happens when you use adlockpessimistic.
Thank You