Preview bug with default params

I have a bunch of reports with four parameters, two integers and two
datetimes. They don't have defaults. I have gone through them and added
another parameter, a string, nullable, with a default of =String.Empty (the
purpose of this is to have a parameter in which I can pass a unique ID, to
avoid caching). When I go to the preview tab in Report Designer, I enter
one of the default-less integer parameters. The parameter section flickers
once. Then I enter the next parameter value. The parameter section now
flickers endlessly, and Visual Studio stops responding. I have to have
Windows forcibly close it down.
If I go to http://localhost/Reports and navigate to the report, I enter the
first parameter value in the textbox, but when I try to move to the next
(hit Tab or click the mouse in the second parameter's input box), I get an
error page: "Reporting Services Error The value provided for the report
parameter <second parameter name here> is not valid for its type.
(rsReportParameterTypeMismatch)". I can hit the browser's Back button and
the value I've entered for the first parameter is still there, so I go to
enter the next parameter value, and then try to move to the third. New
error message about the third parameter, click Back, enter third parameter.
New error message about the fourth parameter, click Back, enter parameter.
What's interesting is up until this point, the text box for the new, default
parameter is disabled. But when I enter the fourth default-less parameter,
the browser clicks and the page refreshes, and now I can enter a value for
the last parameter if I want.DJM,
Sounds like the subsequent param appear dependent on the previous param.
This could lead to the error message being generated, and also the last param
box being disabled prior to the fourth param entry.
I have not suffered this particular problem as I have no linked params.
Hope this assists,
Tony
"DJM" wrote:
> I have a bunch of reports with four parameters, two integers and two
> datetimes. They don't have defaults. I have gone through them and added
> another parameter, a string, nullable, with a default of =String.Empty (the
> purpose of this is to have a parameter in which I can pass a unique ID, to
> avoid caching). When I go to the preview tab in Report Designer, I enter
> one of the default-less integer parameters. The parameter section flickers
> once. Then I enter the next parameter value. The parameter section now
> flickers endlessly, and Visual Studio stops responding. I have to have
> Windows forcibly close it down.
> If I go to http://localhost/Reports and navigate to the report, I enter the
> first parameter value in the textbox, but when I try to move to the next
> (hit Tab or click the mouse in the second parameter's input box), I get an
> error page: "Reporting Services Error The value provided for the report
> parameter <second parameter name here> is not valid for its type.
> (rsReportParameterTypeMismatch)". I can hit the browser's Back button and
> the value I've entered for the first parameter is still there, so I go to
> enter the next parameter value, and then try to move to the third. New
> error message about the third parameter, click Back, enter third parameter.
> New error message about the fourth parameter, click Back, enter parameter.
> What's interesting is up until this point, the text box for the new, default
> parameter is disabled. But when I enter the fourth default-less parameter,
> the browser clicks and the page refreshes, and now I can enter a value for
> the last parameter if I want.
>
>|||How so? It's a brand-new parameter; the existing ones don't reference it in
any way. In fact, *nothing* references this parameter.
"Logicalman" <tony9scott45us@.com7cast.net34> wrote in message
news:E96EC3A4-7308-4AD6-A2C3-F11ADD818D71@.microsoft.com...
> DJM,
> Sounds like the subsequent param appear dependent on the previous param.
> This could lead to the error message being generated, and also the last
> param
> box being disabled prior to the fourth param entry.
> I have not suffered this particular problem as I have no linked params.
> Hope this assists,
> Tony
>
> "DJM" wrote:
>> I have a bunch of reports with four parameters, two integers and two
>> datetimes. They don't have defaults. I have gone through them and added
>> another parameter, a string, nullable, with a default of =String.Empty
>> (the
>> purpose of this is to have a parameter in which I can pass a unique ID,
>> to
>> avoid caching). When I go to the preview tab in Report Designer, I enter
>> one of the default-less integer parameters. The parameter section
>> flickers
>> once. Then I enter the next parameter value. The parameter section now
>> flickers endlessly, and Visual Studio stops responding. I have to have
>> Windows forcibly close it down.
>> If I go to http://localhost/Reports and navigate to the report, I enter
>> the
>> first parameter value in the textbox, but when I try to move to the next
>> (hit Tab or click the mouse in the second parameter's input box), I get
>> an
>> error page: "Reporting Services Error The value provided for the report
>> parameter <second parameter name here> is not valid for its type.
>> (rsReportParameterTypeMismatch)". I can hit the browser's Back button
>> and
>> the value I've entered for the first parameter is still there, so I go to
>> enter the next parameter value, and then try to move to the third. New
>> error message about the third parameter, click Back, enter third
>> parameter.
>> New error message about the fourth parameter, click Back, enter
>> parameter.
>> What's interesting is up until this point, the text box for the new,
>> default
>> parameter is disabled. But when I enter the fourth default-less
>> parameter,
>> the browser clicks and the page refreshes, and now I can enter a value
>> for
>> the last parameter if I want.
>>