Re: Stored Procedures / Oracle / ODBC

I believe that this is where Oracle and SQL*Server are very different. Oracle cannot return a rs from within a stored procedure like SQL*Server can. Oracle stored procedures are self contained and would typically be used to accomplish action tasks. The select statement would have to be coded in VB and the rs opened after the stored procedure completed. Frustrating, isn't it.

So you have yourself both an ODBC limitation and an Oracle stored procedure limitation.

Karl Costenbader wrote:
>
> Vincent Wouters wrote:
> >
> > Can someone tell me how to work with Stored Procedures
> > in a VB4.0/32 environment, working with Data Access Objects.
>
> If ORACLE stored procedures are anything like SQL Server, then the stored
> procedures can have both input and output arguments, but ODBC (as far as
> I have been able to determine) can't handle the output arguments. What > you need to do within the stored procedure is SELECT the data that is to >
be returned from the procedure and then use the OpenRecordset method to > view the results.
> --

           ///
          / ^ \
         ( o-o )
-----oOOO--(_)--OOOo-----------------------------------------------------
                           Todd Bleeker, Just getting by...
      .oooO                http://www.fingerhut.com
      (   )   Oooo.        Line art by Claudio Rodino
-------\ (----(   )------------------------------------------------------
        \_)    ) /
              (_/