@parameter causing problems

[ekta22]

Hi,

Our reports were developed in crystal version 8.5 using SQL Server 2000 as the database. Recently we upgraded all our reports to version 10 and everything works fine. These reports run on the web. Recently we created a new report in version 10 and that is based on a stored procedure in our SQL 2000 database. When I run this report on my desktop it runs fine and returns data but if I run it on the web, report is blank. It is as if it is not reading the parameters entered by the user at all. When I look at the parameters for this report they all have @ sign in front of them...@STRAT_DATE, @END_DATE etc...
But my other reports that were upgraded from version 8.5 to 10 do not have the @ sign in front. For some reason version 10 adds @ sign in front of the parameters. Does anyone has any as to what is going on here and how to fix this problem?

Thanks

 

[paulmarr]

Sounds like during the conversion - somehow Crystal is using report parameters instead of the stored procedure's parameters. Therefore - no values are being passed to the stored proc - only the report - no stored proc parameter values - no data.

Check the record selection of the report (it shouldn't have one) - remove the Crystal created parameters if necessary and refresh the report.

I hope this helps

Cheers
paulmarr

 

[ekta22]

Hi paul,

Thanks for the reply. The report that is not running was not converted. It was created in version 10. It seems that is not making a connection with the stored procedure. I don't have anything for the record selection. It is empty. What do you mean by removing Crystal created parameters? Parameters were created in the stored procedure and not in Crystal. Any other thoughts?

Thanks