How can you get around this?  Have your parameters selected by the user in your web page (here you can apply security as to what they can see), pass them to a stored proc (again, you can pass the session variables as well and have the stored proc apply any security as needed as well) and set the dataset/datatable returned from the stored proc as the datasource of the report.  As long as the data is in the format desired, CR will use it (ie you don't need to connect CR to a database if you don't want to)

 

HTH

 

sorry.

 

Connecting to your database and calling a stored proc is really outside the scope of these forums (there are better references on the web).  The rest is creating an instance of the report, setting the output of the stored proc to the DataSource of the Report (this is heart of solution) and then setting reportViewer to use the report instance is the basic outline.

 

Use a datasource type of ADO.NET for the report.