I have a report created in crystal reports XI. It is based off a stored procedure with parameters. One of the parameters being a ref cursor. I can get the report to work fine with the native db provider. However, I need to make this report work through a vendor product that requires the use of OraOLEDB as the provider. When I switch to OraOLEDB, I get an error when setting the database location and filling in the parameters. The error is PLS-00306 Wrong number or types of arguments, etc. To determine the problematic parameters, I removed them one an a time. The date parameters were a problem, but I got around that by changing the data types in the stored procedure to varchar2 instead of date. However, the ref cursor parameter is another problem that yields the same PLS-00306 error. I've seen tons of documentation on ref cursors working fine with OraOLEDB in .net, asp, etc. So it seems a ref cursor will not work with a combination of OraOLEDB and Crystal. How can I get around this issue?
I'm experimenting with the stored proc and changed it to write to a table instead of a ref cursor. But how do you get crystal to run a stored procedure, then base the report fields off the table the sp wrote to? I'm at a loss here as to how to work around this issue. Thanks for any help you can provide!