Parameters & ReportingService.Render

My report has 2 parameters. One I would like to set the value of in my vb
code, the other I would like to be queried according to the report design.
In the designer the first parameter is non-queried and will allow blank but
not null. The second is "from query". Obviously everything works in the
designer. ;) The 2nd parameter dropdown list is correctly populated from
the query that's embedded in the report design.
My <DeviceInfo> has toolbar=true, parameters=true.
I have tried several things. In all cases parameters(1).value = <correct
value>.
1) parameters(2).Value = Nothing. Error is "Default value or value provided
for the report parameter 'TDN' is not a valid value."
2) parameters(2).value = "". Error is the same as #1.
3) parameters(2).value = " ". Error is the same as #1.
4) parameters(2).value = "C100". This is a typical value for this field,
but won't be accurate in all situations. same error.
5) leave off parameter(2) in the vb code. Error is "This report requires a
default or user-defined value for the report parameter 'TDN'. To run or
subscribe to this report, you must provide a parameter value."
6) paraamters(2).value = "". check "default" and "null" in Report Manager.
Error is "Default value or value provided for the report parameter 'TDN' is
not a valid value."
Can anyone shed some light on this?
Thanks."Joe" wrote:
> My report has 2 parameters. One I would like to set the value of in my vb
> code, the other I would like to be queried according to the report design.
> In the designer the first parameter is non-queried and will allow blank but
> not null. The second is "from query". Obviously everything works in the
> designer. ;) The 2nd parameter dropdown list is correctly populated from
> the query that's embedded in the report design.
Look inside the YourReport.rdl (View Code) and double check the
ReportParameter names in the xml. You should find your two, case sensitive
parameter names.
If one is called parameter1 instead of your name, or additional entries, try
changing it to what you want, then redeploy the report and retry your code.
Sometimes the Query Designer has a mind of its own with parameters, and has
messed up working rdl files. <g>
I hope this is of some help to you.