FIX: ADO Client Cursors Report LockType = adLockPessimistic (190625)
The information in this article applies to:
- ActiveX Data Objects (ADO) 1.5
- ActiveX Data Objects (ADO) 2.0
- ActiveX Data Objects (ADO) 2.1
- ActiveX Data Objects (ADO) 2.5
- ActiveX Data Objects (ADO) 2.6
- ActiveX Data Objects (ADO) 2.7
- Microsoft Visual Basic Professional Edition for Windows 5.0
- Microsoft Visual Basic Professional Edition for Windows 6.0
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
This article was previously published under Q190625 SYMPTOMS
ActiveX Data Objects (ADO) incorrectly reports that a client-side recordset
opened with a LockType of adLockPessimistic was opened with pessimistic
locking.
The ADO client cursor engine does not support pessimistic locking. If you
ask ADO for a pessimistically locked client-side recordset, you actually
receive an optimistically locked recordset instead, even though ADO did not
change the value of the LockType property to adLockOptimistic.
With MDAC 2.1 sp2 the locktype is now returned as adlockbatchoptimistic(4).
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article.
This bug has been fixed in MDAC 2.1 Service Pack 2 and later releases.
REFERENCES
ADO 2.0 documentation
Modification Type: | Minor | Last Reviewed: | 3/2/2005 |
---|
Keywords: | kbADO210sp2fix kbbug kbDatabase kbDSupport kbMDAC210SP2fix KB190625 |
---|
|