Skip to Content
0
Former Member
Feb 26, 2010 at 09:31 PM

Stored procedure parameter issue when switch from Oracle and SQL

24 Views

Hello All,

We support two databases in our application SQL Server and Oracle. Before users run our Crystal reports we update connection information (in code) for each report table to the current database and then execute the report. The problem is when we use stored procedures that take arguments Crystal report doesnu2019t seem to update the parameter name when the underlying database name/type is changed. So for SQL Server a parameter begins with u201C@paramNameu201D and in Oracle itu2019s without the u201C@u201D sign. Weu2019ve tried removing the parameters and reading but the API throws an exceptions such as u201CYou cannot add, remove or modify parameter fields using this method. Please modify the report directly.u201D or u201CNot Supported.u201D

Any suggestions are appreciated.

Thanks in advance.