Microsoft KB Archive/193872

= BUG: VB6 Version of RDO Cannot Access Oracle Packages =

Article ID: 193872

Article Last Modified on 5/13/2003

-

APPLIES TO


 * Microsoft Visual Basic 6.0 Learning Edition
 * Microsoft Visual Basic 6.0 Professional Edition
 * Microsoft Visual Basic 6.0 Enterprise Edition

-



This article was previously published under Q193872



SYMPTOMS
When 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.

The previous bug prevented access to Oracle stored procedures through RDO when using the. syntax. Currently you can access a stored procedure through RDO using. but you are now unable to access parameterized stored procedures using the. syntax.

The exceptions to the above statement are if you are calling an Oracle stored procedure with no parameters, or if you are using the "resultsets from stored procedure" functionality with NO input parameters. Please see the REFERENCES section of this article for information. Under these circumstances everything works as expected, with no errors.



RESOLUTION
There 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. , ., and even. ..



STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

