Cascading Parameters

All of a sudden I am having problems with cascading parameters. This report,
under development, was working fine earlier in the week. I've started over
and each time I get the same problem. I've been working with cascding
parameters for some time and nver seen this. I've tried everything but can't
get it back working correctly.
I have a cascading parameter that rlies on a date parameter. When I key in
the parameter, the cascading parameter populates the dropdown on the report
but when I click in the next parameter text box to set focus, Visual studio
has a seizure and starts flashing and by cpu maxes out. When I run the same
report in reporting services, I get an error that the next parameter has an
inconsistent data type.
I'm confused. Can anyone help."Mardy" wrote:
> All of a sudden I am having problems with cascading parameters. This report,
> under development, was working fine earlier in the week. I've started over
> and each time I get the same problem. I've been working with cascding
> parameters for some time and nver seen this. I've tried everything but can't
> get it back working correctly.
> I have a cascading parameter that rlies on a date parameter. When I key in
> the parameter, the cascading parameter populates the dropdown on the report
> but when I click in the next parameter text box to set focus, Visual studio
> has a seizure and starts flashing and by cpu maxes out. When I run the same
> report in reporting services, I get an error that the next parameter has an
> inconsistent data type.
> I'm confused. Can anyone help.|||More information. If I tab between the parameter text boxes, I can set the
dependent parameter and the report runs. Any subsequent click leads to Visual
Studion convulsions. WEIRD
"Mardy" wrote:
> All of a sudden I am having problems with cascading parameters. This report,
> under development, was working fine earlier in the week. I've started over
> and each time I get the same problem. I've been working with cascding
> parameters for some time and nver seen this. I've tried everything but can't
> get it back working correctly.
> I have a cascading parameter that rlies on a date parameter. When I key in
> the parameter, the cascading parameter populates the dropdown on the report
> but when I click in the next parameter text box to set focus, Visual studio
> has a seizure and starts flashing and by cpu maxes out. When I run the same
> report in reporting services, I get an error that the next parameter has an
> inconsistent data type.
> I'm confused. Can anyone help.|||Tested further on my other laptop. It's Reporting Services sp1 versus sp2 on
the problem machine. The SP1 machine is more stable. No Visual Studio
convusling.
SH**
"Mardy" wrote:
> More information. If I tab between the parameter text boxes, I can set the
> dependent parameter and the report runs. Any subsequent click leads to Visual
> Studion convulsions. WEIRD
> "Mardy" wrote:
> > All of a sudden I am having problems with cascading parameters. This report,
> > under development, was working fine earlier in the week. I've started over
> > and each time I get the same problem. I've been working with cascding
> > parameters for some time and nver seen this. I've tried everything but can't
> > get it back working correctly.
> >
> > I have a cascading parameter that rlies on a date parameter. When I key in
> > the parameter, the cascading parameter populates the dropdown on the report
> > but when I click in the next parameter text box to set focus, Visual studio
> > has a seizure and starts flashing and by cpu maxes out. When I run the same
> > report in reporting services, I get an error that the next parameter has an
> > inconsistent data type.
> >
> > I'm confused. Can anyone help.|||I have found that it depends on my cascading parameters whether this
happens. It doesn't always happened. I haven't been developing on a report
with this problem in SP2 so I can't say if it is better or worse. What I can
say is that it only occurs when developing. If you deploy it, it will work
just fine. So, for a report that does this I would just deploy it for
testing. A bit of a pain but it is a workaround and the report will work
fine in production.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mardy" <Mardy@.discussions.microsoft.com> wrote in message
news:938D29C2-34FA-4843-B74F-D0C95B09BFC2@.microsoft.com...
> Tested further on my other laptop. It's Reporting Services sp1 versus sp2
> on
> the problem machine. The SP1 machine is more stable. No Visual Studio
> convusling.
> SH**
> "Mardy" wrote:
>> More information. If I tab between the parameter text boxes, I can set
>> the
>> dependent parameter and the report runs. Any subsequent click leads to
>> Visual
>> Studion convulsions. WEIRD
>> "Mardy" wrote:
>> > All of a sudden I am having problems with cascading parameters. This
>> > report,
>> > under development, was working fine earlier in the week. I've started
>> > over
>> > and each time I get the same problem. I've been working with cascding
>> > parameters for some time and nver seen this. I've tried everything but
>> > can't
>> > get it back working correctly.
>> >
>> > I have a cascading parameter that rlies on a date parameter. When I key
>> > in
>> > the parameter, the cascading parameter populates the dropdown on the
>> > report
>> > but when I click in the next parameter text box to set focus, Visual
>> > studio
>> > has a seizure and starts flashing and by cpu maxes out. When I run the
>> > same
>> > report in reporting services, I get an error that the next parameter
>> > has an
>> > inconsistent data type.
>> >
>> > I'm confused. Can anyone help.|||I found this issue occurs after applying MS patch 05-014 to my XP desktop
client and using IE browser. I have not found the solution yet, but we are
running Report Services SP1 as well.
"Mardy" wrote:
> All of a sudden I am having problems with cascading parameters. This report,
> under development, was working fine earlier in the week. I've started over
> and each time I get the same problem. I've been working with cascding
> parameters for some time and nver seen this. I've tried everything but can't
> get it back working correctly.
> I have a cascading parameter that rlies on a date parameter. When I key in
> the parameter, the cascading parameter populates the dropdown on the report
> but when I click in the next parameter text box to set focus, Visual studio
> has a seizure and starts flashing and by cpu maxes out. When I run the same
> report in reporting services, I get an error that the next parameter has an
> inconsistent data type.
> I'm confused. Can anyone help.|||I am having the same issue. I found by putting in a default value for the
parameter, I can bypass the dropdown selection. I have this issue both in
SP1 and SP2.
Looking forward to a patch,
andy
"Mardy" <Mardy@.discussions.microsoft.com> wrote in message
news:1A67CB60-5CB8-4AD7-9B2E-F42530880DD2@.microsoft.com...
> All of a sudden I am having problems with cascading parameters. This
> report,
> under development, was working fine earlier in the week. I've started
> over
> and each time I get the same problem. I've been working with cascding
> parameters for some time and nver seen this. I've tried everything but
> can't
> get it back working correctly.
> I have a cascading parameter that rlies on a date parameter. When I key in
> the parameter, the cascading parameter populates the dropdown on the
> report
> but when I click in the next parameter text box to set focus, Visual
> studio
> has a seizure and starts flashing and by cpu maxes out. When I run the
> same
> report in reporting services, I get an error that the next parameter has
> an
> inconsistent data type.
> I'm confused. Can anyone help.