Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
johnb
Starting Member
8 Posts |
 Posted - 2005-01-06 : 09:16:36
|
| Hello and Happy New Year,The problem I'm having is when I pass some parameters (say 2) to a report that requires more (say 4). The odd thing is that in the VS preview all works (2 parameters are filled with 2 to be filled) but when I deploy and run through the web nothing works - the report title is shown but there is no report or area to fill the parameters?Has anyone else had this problem and if so found how to fix it?SP1 is installed on the report server.ThanksJohn |
|
|
jhermiz
3564 Posts |
Posted - 2005-01-06 : 10:43:46
|
| Have you tried restarting the reporting server ?A new beat on the web -- http://www.web-impulse.com |
 |
|
|
johnb
Starting Member
8 Posts |
Posted - 2005-01-06 : 11:17:27
|
| Yes I have but it didn't resolve.John |
|
|
|
Franco Well
Starting Member
23 Posts |
Posted - 2005-01-11 : 11:23:20
|
| Does your Where clause contain code similiar to this to account for the empty parameters?Where (@Provider = '' or p.Provider = @Provider) and (@Member = '' or s.Member = @Member) and (@PSCode = '' or s.PS_Code = @PSCode) and (@Location = '' or s.Location = @Location)Franco |
|
|
|
jhermiz
3564 Posts |
Posted - 2005-01-11 : 11:38:00
|
Franco you should use IS NULL and send NULL as a default parameter to your sproc.
Keeping the web experience alive -- [url]http://www.web-impulse.com[/url]
|
|
|
|
Franco Well
Starting Member
23 Posts |
Posted - 2005-01-11 : 12:16:23
|
| JhermizSo that I can learn what you are referring to, please convert my code sample to the way it would read using your suggestion .Thanks....Franco |
|
|
|
jhermiz
3564 Posts |
Posted - 2005-01-11 : 13:16:54
|
Where (@Provider = '' or p.Provider = @Provider)and (@Member = '' or s.Member = @Member)and (@PSCode = '' or s.PS_Code = @PSCode)and (@Location = '' or s.Location = @Location)Should be:WHERE (@Provider IS NULL OR p.Provider = @Provider)AND (@Member IS NULL OR s.Member = @Member)AND (@PSCode IS NULL OR s.PS_Code = @PSCode)AND (@Location IS NULL OR s.Location = @Location)When you pass the parameters into the procedure set them as null in the defaults:@Provider varchar(50)=NULL, @Member varchar(50) = NULL...etcJon
Keeping the web experience alive -- [url]http://www.web-impulse.com[/url]
|
|
|
|
Franco Well
Starting Member
23 Posts |
Posted - 2005-01-11 : 13:45:18
|
| JonThanks!Franco |
|
|
|
johnb
Starting Member
8 Posts |
Posted - 2005-01-12 : 07:29:46
|
| Thanks for the help.I'm using a query that is based upon views rather than sprocs. I don't think anything is wrong with the reports themselves as they are working OK in the preview part of Visual Studio.I was wondering if there were any Report Manager settings to do with sub-reports and passing parameters that may resolve the problem. I've tried the parameter settings within the reports properties but they haven't fixed it. |
|
|
|
|
|
|
Passing 'some' Parameters