whenever trying to call my Oracle stored procedure from Cold Fusion. I
received this error in one stored procedure, fixed it, and then got it
with another stored procedure.
Both of the stored procedures, as it turned out, were in the same
package body in Oracle. I separated them out of the package body, and
this seems to have resolved the issue.
I have many, many other issues getting Oracle to work successfully with
Cold Fusion (a large part of the problem is the really bizarre database
design that I've inherited), but I'm smashing my way through them one by
one.
--
Richard S. Crawford
Programmer III,
UC Davis Extension Distance Learning Group (http://unexdlc.ucdavis.edu)
(916)327-7793 / [EMAIL PROTECTED]
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
