BUG: SNAOLEDB Does Not Support Pessimistic Locking (249167)
The information in this article applies to:
- Microsoft OLE DB Provider for AS/400 and VSAM 4.0 SP2
- Microsoft OLE DB Provider for AS/400 and VSAM 4.0 SP3
This article was previously published under Q249167 SYMPTOMS
The Microsoft OLEDB Provider for AS/400 and VSAM (SNAOLEDB) does not support pessimistic locking.
In the Microsoft SNA SDK documentation under the "ADO Recordset Object in the OLE DB Provider for AS/400 and VSAM" topic, it is mentioned under LockType that SNAOLEDB supports all four lock types. Namely adLockReadOnly, adLockOptimistic, adLockPessimistic, and adLockBatchOptimistic. The preceding statement is not true and SNAOLEDB does not currently support adLockPessimistic from an ADO recordset object.
The ADO Client side cursor does not support "pessimistic" locking. ADO server side cursor support "pessimistic" locking if the corresponding provider supports this property. SNAOLEDB does not support "pessimistic" locking. If an unsupported value is set, then no error occurs and the closest supported LockType is used instead. If from an ADO program you set the LockType property to adLockPessimistic, when you open an updateable recordset with server side cursor it automatically maps to either adLockOptimistic or adLockBatchOptimistic.
STATUS
Microsoft has confirmed this to be a problem in the Microsoft SNA Server version 4.0 Service Pack 2 (SP2) and Service Pack 3 (SP3) SDK documentation.
REFERENCES
For more information, please refer to the following article in the Microsoft Knowledge Base:
190625 FIX: ADO Client Cursors Report LockType = adLockPessimistic
SNA SDK Documentation
Modification Type: | Minor | Last Reviewed: | 11/24/2004 |
---|
Keywords: | kbbug kbpending KB249167 |
---|
|