The information in this article applies to:
SYMPTOMSWhen using the Visual Basic 6.0 version of RDO 2.0 with the Microsoft Oracle ODBC Driver (that shipped with Visual Basic 6.0), you cannot access a procedure within a Oracle package if the procedure has Input or Output parameters that are passed. CAUSE
This bug was caused by a fix that was implemented for a different bug in
the version of RDO that shipped with Visual Basic 5.0. Please see the
REFERENCES section of this article for information on that bug.
RESOLUTIONThere is no workaround for this bug in the version of RDO v2.0 that ships with Visual Basic 6.0. If you need to access Oracle packages in a Visual Basic 6.0 application, it is recommended that you switch to ADO. With ADO 1.5 and 2.0 you have complete access to Oracle stored procedures using <schema>.<procedure>, <package>.<procedure>, and even <schema>.<package>.<procedure>. STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. REFERENCES
For additional information, please see the following articles in the
Microsoft Knowledge Base:
Q175018 : HOWTO: Acquire and Install the Microsoft Oracle ODBC Driver Additional query words: kbDSupport kbdse kbVBp kbVBp600 kbVBp500 kbVBp600 kbRDO200bug kbRDO150
Keywords : kbGrpVBDB |
Last Reviewed: January 5, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |