Unanswered: CommandBuilder.Derive Parameters does not work with Oracle Stored Procedure
I am trying to use the DeriveParameters() method to
populate the parameter list of a OleDbCommand which will
call into an Oracle stored procedure within a package. I
am using the Microsoft OLEDB Provider for Oracle and an
Oracle 9.2.0 database.
Apparently, when the procedure is within a package, the
DeriveParameters() function fails silently. It does not
throw an exception, but the Parameters collection of the
OleDbCommand is cleared out. If I attempt to call a global
procedure (one that is not in a package) the call succeeds.
Does anyone know if this is a problem in OLE DB? In
ADO.NET? In Oracle? Is there a way to get around this?
Hardcoding the parameters is really not feasible, as the
procedure is made available through a user interface that
dynamically builds a screen for the user to enter
information -- it wouldn't be very maintainable (or
practical) to hardcode the parameters for all possible