Article ID: 283842 - View products that this article applies to.
This article was previously published under Q283842
This article has been archived. It is offered "as is" and will no longer be updated.
With the Microsoft OLE DB Provider for Oracle (MSDAORA), the execution of a SQL statement that contains both an IN and a UNION clause may produce an ActiveX Data Objects (ADO) Recordset object that contains an incorrect number of columns.
This problem occurs when using an ADO client-side cursor (which means that the CursorLocation property is set to adUseClient) but works correctly when using a server-side cursor.
To resolve this problem, obtain the latest service pack for Microsoft MDAC 2.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
293312To 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:
(https://support.microsoft.com/kb/293312/EN-US/ )INFO: How to Obtain the Latest MDAC 2.5 Service Pack
(https://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:
Version Size File name Platform ------------------------------------------------------- 2.53.6007.0 209,168 Msdaora.dll x86
The problem does not occur if you use a server-side cursor; the CursorLocation property is set to adUseServer.
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 2, MDAC 2.5 SP3, and MDAC 2.7.
Steps to Reproduce the Behavior
Article ID: 283842 - Last Review: January 5, 2015 - Revision: 6.1