Hi, I work on a vb6 software accessing sql server 2000 with ado2.6 ... and I struggle with a weird problem ... When changes are done by two "users" on the same field of one record, usually the first update is accepted and the second raises the error -2147217864 like in this example : ------ strSql = "SELECT DISTINCT * FROM Shippers WHERE ShipperID=2" rc1.CursorLocation = adUseClient rc2.CursorLocation = adUseClient rc1.Open strSql, con, adOpenStatic, adLockOptimistic rc2.Open strSql, con, adOpenStatic, adLockOptimistic rc1!CompanyName = "Test1" rc2!CompanyName = "Test2" rc1.Update rc2.Update ------ But the same kind of code (clientside recordsets with optimistic lock) doesn't work with the sql server database I currently use at work ... The first update is accepted, then the second update is skipped without any error message. Why this error is not generated ? Does anyone have an idea ? Thanks in advance (and sorry for the english)