View Single Post
  #3 (permalink)  
Old March 2nd, 2006, 10:31 AM
dba123 dba123 is offline
Authorized User
Join Date: Feb 2006
Location: , , .
Posts: 16
Thanks: 0
Thanked 0 Times in 0 Posts

If I put that in my SQL code, then basically I'll have different stored procs to filter out certain companies for each table in my report. The problem I see with that, is how would I ever parameterize the report then...provide a way for them to change companies on the fly on the reporting UI side using SSRS 2005 Report Param prompts? What I am afraid is, if I code all in SQL, then I loose the ability to provide prompts on the UI side to the user to change criteria on the fly, since everying coming into the report has already been hard coded such as dates, companies, etc. type of criteria. Is this a valid concern or ist here an approach that still lets me code this in SQL but also still allow them to change params even though stuff is hard coded before it's imported via the SSRS datasets I create for those stored procs?

Reply With Quote