>Hi, William
>
>Are you saying that in scenario 1, you'd want the report to detect 1 set of parms, and in scenario 2, you'd want the report to detect a 2nd set of parms?
>
>Out of curiosity, can you describe the parameters?

Here's my simplest situation.

I have a report that has a string parameter named well_Field. In the report definition (in BIDS) the parameter is defined with available values coming from a query from one of the datasets.

If I define the parameter as Visible, I can access the report through Report Manager, pick the well_field from the parameter dropdown, and the report runs w/o problem.

If I try to run the report via a URL with the parameter in the URL - in this case something like http://nt00devweb03/ReportServer_FALKIRK_R2/Pages/ReportViewer.aspx?/Falkirk_Reports/WaterSupplyWellandSpring&rs:Command=Render&well_Field=300A
I get an error that the report parameter is undefined..

CRAP. I just recreated the parameter (for about the 20th time) to run it to get the exact error message. Now it works.

I spent a couple of hours Friday fighting with this.

Nevermind I guess?

Thanks for trying.