December 11, 2008 at 7:10 am
We have a report that needs to pass multiple multi valued parameters to a stored procedure so that based off of one of the parameters, a different query is selected to return the proper data. We have tried several of the stock splitting stored procs that are out on the forums, but when we run the report we get no data returned, when we should get several thousand rows. When we run the stored proc by itself and manually enter comma separated values for the parameters, it returns results, but the report itself will not return anything. Does anyone have any suggestions on how to pass this information down to the stored proc or what values I can set in the profiler to see what is happening once the report is run? Thank you.
Kurt
December 11, 2008 at 7:31 am
Write the parameter values to a table.
December 11, 2008 at 7:41 am
blk_phoenix (12/11/2008)
We have a report that needs to pass multiple multi valued parameters to a stored procedure so that based off of one of the parameters, a different query is selected to return the proper data. We have tried several of the stock splitting stored procs that are out on the forums, but when we run the report we get no data returned, when we should get several thousand rows. When we run the stored proc by itself and manually enter comma separated values for the parameters, it returns results, but the report itself will not return anything. Does anyone have any suggestions on how to pass this information down to the stored proc or what values I can set in the profiler to see what is happening once the report is run? Thank you.Kurt
Definitively run profiler and capture the call to your proc. Make sure it is passing in the values you think it should be. Copy it and run it manually to make sure it works. It will at least help narrow down the problem.
December 11, 2008 at 8:27 am
We found out the problem. In the stored proc, the variables were not set to the appropriate size to accept the parameters comming in from RS. Everything runs great now that it is fixed. Thanks for the replys.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply