rcampbellwhite
Programmer
I just upgraded from Crystal Reports.Net that shipped with Visual Studio 2003 to Crystal Reports.Net v10.0. I upgraded because of two known PDF rendering bugs that were preventing me from being able to roll my reports into production - string fields being inexplicably truncated in the report, and graphics being rendered incredibly poorly. Fortunately both of these issues were resolved by the upgrade and my reports were looking really good as a result.
However, I stumbled across a bit of a show-stopper in that one of my reports was suddenly ignoring the stored proc parameters that I was passing to it, thereby resulting in a report that always showed the same content.
My first stop was the Business Objects .Net Developer Zone. A bit of browsing turned up the How To page, which included a link to a knowledge base article published on 23 Feb 2004 entitled "Report not accepting new stored procedure parameters values in .NET application". This article suggested using the .Refresh method on the report document object at runtime. I tried it, but no joy.
I then thought I'd take it back to basics and see exactly what stored proc call was being fired at my SQL Server by the report. Using SQL Profiler I saw that the report was passing the same value for one parameter regardless of what I was specifying it should pass via my front-end application. This made me wonder about default values in the report, and therein lay the answer to my problem. The report had saved default values included in its definition. These were overriding my passed parameter values. As soon as I deleted the default values and recompiled my application it all started working properly again.
Not really desirable behaviour, but at least my reports are working again now!
I hope this helps someone avoid the same amount of frustration that my Friday morning has just consisted of!
Rob C-W
However, I stumbled across a bit of a show-stopper in that one of my reports was suddenly ignoring the stored proc parameters that I was passing to it, thereby resulting in a report that always showed the same content.
My first stop was the Business Objects .Net Developer Zone. A bit of browsing turned up the How To page, which included a link to a knowledge base article published on 23 Feb 2004 entitled "Report not accepting new stored procedure parameters values in .NET application". This article suggested using the .Refresh method on the report document object at runtime. I tried it, but no joy.
I then thought I'd take it back to basics and see exactly what stored proc call was being fired at my SQL Server by the report. Using SQL Profiler I saw that the report was passing the same value for one parameter regardless of what I was specifying it should pass via my front-end application. This made me wonder about default values in the report, and therein lay the answer to my problem. The report had saved default values included in its definition. These were overriding my passed parameter values. As soon as I deleted the default values and recompiled my application it all started working properly again.
Not really desirable behaviour, but at least my reports are working again now!
I hope this helps someone avoid the same amount of frustration that my Friday morning has just consisted of!
Rob C-W