Article ID: 274423 - View products that this article applies to.
This article was previously published under Q274423
When fetching rowset values into nonvariant datatypes, ActiveX Data Objects (ADO) may suppress errors that are related to the status of the recordset, such as notifications that the record is locked by another user.
This problem occurs in Microsoft Data Access Components (MDAC) version 2.50.4403.12 (Microsoft Windows 2000/MDAC 2.5 RTM) and 2.51.5303.5 (Windows 2000/MDAC 2.5 SP1). This problem does not occur in MDAC version 2.60.6526.3 (MDAC 2.6 RTM).
A slightly different code path is taken depending on whether the application is fetching into variant datatypes. The use of variants is wrapped in an internal context object which has the ability to return error information. Nonvariants do not have this context wrapper and do not return error information.
To resolve this problem, obtain the latest service pack for Microsoft Data Access Components 2.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
293312The English version of this has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
(http://support.microsoft.com/kb/293312/ )INFO: How to Obtain the Latest MDAC 2.5 Service Pack
Date Version Size File name ---------------------------------------------------------- 8/29/2000 2.51.5629.0 20,480 bytes Msader15.dll 8/29/2000 2.51.5629.0 487,696 bytes Msado15.dll 8/29/2000 2.51.5629.0 172,304 bytes Msadomd.dll 8/29/2000 2.51.5629.0 57,616 bytes Msador15.dll 8/29/2000 2.51.5629.0 184,592 bytes Msadox.dll 8/29/2000 2.51.5629.0 57,616 bytes Msadrh15.dll 8/29/2000 2.51.5629.0 94,480 bytes Msjro.dll
WORKAROUNDThere is no workaround for this issue.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Data Access Components 2.5 Service Pack 2.
Steps to Reproduce Behavior
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/247757/EN-US/ )FIX: Connection Leak Using Parameterized Command In ADO
(http://support.microsoft.com/kb/264442/EN-US/ )FIX: ADO Recordset Loses Filter Property When Marshalled In-Proc
(http://support.microsoft.com/kb/264701/EN-US/ )FIX: Passing ADO Recordset ByRef Resets Error Information
Article ID: 274423 - Last Review: September 26, 2005 - Revision: 2.2