ADO overwriting locked record problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all,

I have a problem with ADO. I am updating a ADO recordset in a multi-user
environment but somehow it seems that the code I am using is ignoring locks
by other users.

This is the code I am using

dim cnx as ADODB.connection
dim myRs as ADODB.recordset

set cnx = currentproject.connection
set myrs = new adodb.recordset
cnx.BeginTrans

With rs
.Fields("FIELD1") = "VALUE1"
.Update
End With

If cnx.Errors.Count <> 0 Or Err.Number <> 0 Then
cnx.RollbackTrans
Else
cnx.CommitTrans
End If

Somehow this code seem to update the table, although someone else is already
updating the table (and locking the record via another instance). I can not
figure out why!!!! Can anybody please help?

TIA
 
In
Brotha Lee said:
Hi all,

I have a problem with ADO. I am updating a ADO recordset in a
multi-user environment but somehow it seems that the code I am using
is ignoring locks by other users.

This is the code I am using

dim cnx as ADODB.connection
dim myRs as ADODB.recordset

set cnx = currentproject.connection
set myrs = new adodb.recordset
cnx.BeginTrans

With rs
.Fields("FIELD1") = "VALUE1"
.Update
End With

If cnx.Errors.Count <> 0 Or Err.Number <> 0 Then
cnx.RollbackTrans
Else
cnx.CommitTrans
End If
Click to expand...

That's not your code. It's obviously a transcription of part of the
code. If there were something relevant in the code you omitted, we
wouldn't know about it.
Somehow this code seem to update the table, although someone else is
already updating the table (and locking the record via another
instance). I can not figure out why!!!! Can anybody please help?
Click to expand...

How do you know that the record is locked by another user? If the other
user is editing the record but using optimistic locking, then the record
won't be locked until the moment that the user saves the record.
 
How do you know that the record is locked by another user? If the other
user is editing the record but using optimistic locking
Click to expand...

Hint for the OP: test the recordset object's LockType property *after*
it has been opened you may *think* it is adLockPessimistic...)

Jamie.

--
 
Back
Top