When you use the OleDb providers, you can simply consume the returned ref
cursor as a DataTable.
With the OracleClient provider, you have to specify the ref_cursor as an
output parameter. There is no need to actually consume this parameter, as
you will receive your output through normal means once you send in the
properly named ref cursor output parameter, but the param has to be there to
link the MS world with the Oracle world.
If I remember correctly, the same is true with ODP.NET.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***********************************************
Think Outside the Box!
***********************************************
"JV" <jo**********@goisc.com> wrote in message
news:eB**************@tk2msftngp13.phx.gbl...
A ref cursor data type can obviously be returned as an output parameter of
a stored procedure, but can an ASP.NET application call an oracle proc that
uses a ref cursor as an input parameter? If so, how? What object do you
pass as that parameter?
We are using System.Data.OracleClient, but if necessary, we might be able
to switch.
