Article ID: 291014 - View products that this article applies to.
This article was previously published under Q291014
This article has been archived. It is offered "as is" and will no longer be updated.
When using the ActiveX Data Objects for Windows Foundation Classes (ADO/WFC) to access a database, specific error codes are not returned when exceptions are thrown. With ADO 2.5 and 2.6, all errors are returned as the following:
The exact error code may differ, depending on the cause of the particular problem.
The IErrorInfo interface is not correctly exposed in ADO 2.5 and ADO 2.6. As a result, the WFC classes are unable to get details of the exception, causing WFC to report a more generic error.
To resolve this problem, obtain the latest service pack for Microsoft Data Access Components 2.6. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/300635/EN-US/ )INFO: How to Obtain the Latest MDAC 2.6 Service Pack
HotfixThe English version of this fix should have the following file attributes or later:
NOTE: This fix should only be applied to computers currently running Microsoft Data Access Components (MDAC) version 2.6. At this time, a fix is not available for MDAC 2.5 computers.
Date Time Version Size File name ------------------------------------------------------------- 02/20/01 20:53 2.61.7219.0 528,656 bytes Msado15.dll 04/11/01 304,128 bytes Q291014_MDAC26_SP1_x86_en.exe
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.6 Service Pack 1.
Steps to Reproduce BehaviorThe following Visual J++ code can be used to illustrate the problem:
Before applying the fix, the error described in the "Symptoms" section of this article is displayed when the above code is run.
After the fix has been applied, this code produces the following error instead:
This message is correct, because we are requesting an invalid field name.
Item cannot be found in the collection corresponding to the requested name or ordinal.
Article ID: 291014 - Last Review: February 27, 2014 - Revision: 1.2
Contact us for more help
Connect with Answer Desk for expert help.