Reporting Services Designer problem

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Chris McKenzie - 21 Sep 2005 22:50 GMT

I'm having a serious problem with the Reporting Services designer. I have a
report with 2 parameters offered as dropdown lists. The first time I go into
the designer, I can change the value of the dropdownlists (with some
flashing behavior that doesn't make sense) and execute the report. However,
if I go back to the layout tab and then return to the Preview tab and do the
same thing, the designer acts like its caught in some kind of endless loop.
It flashes constantly as if refreshing the paramters list, locks up Visual
Studio completely, and continues to consume memory. I end up having to kill
devenv.exe in the task manager to get anything done

Is there a fix for this?

I'm using VIsual Studio 2003 and Sql Server Reporting Services Developer
Edition SP2.

I can provide a sample dataset and rdl file to Microsoft if it becomes
necessary.

Thanks,
Chris McKenzie

Reply to this Message

Bruce L-C [MVP] - 21 Sep 2005 23:15 GMT

I have had that on occasion. The good news is it is only a problem in
design, it will work in production. When I have a report that does this I
deploy and test and don't use the preview in the designer. At least it is a
workaround. I haven't tried this in RS 2005 to see if the problem went away.

Signature

Bruce Loehle-Conger
MVP SQL Server Reporting Services

> I'm having a serious problem with the Reporting Services designer. I have
> a report with 2 parameters offered as dropdown lists. The first time I go
[quoted text clipped - 16 lines]
> Thanks,
> Chris McKenzie

Reply to this Message

Chris McKenzie - 22 Sep 2005 13:16 GMT

Aye, that's what I ended up having to do to get my work done. Do you know if
this is a known bug?

Chris

>I have had that on occasion. The good news is it is only a problem in
>design, it will work in production. When I have a report that does this I
[quoted text clipped - 23 lines]
>> Thanks,
>> Chris McKenzie

Reply to this Message

Bruce L-C [MVP] - 22 Sep 2005 15:55 GMT

I'll try to find a report of mine that does this and see if it still does it
in RS 2005.

Signature

Bruce Loehle-Conger
MVP SQL Server Reporting Services

> Aye, that's what I ended up having to do to get my work done. Do you know
> if this is a known bug?
[quoted text clipped - 28 lines]
>>> Thanks,
>>> Chris McKenzie

Reply to this Message

Ben Sullins - 22 Sep 2005 17:43 GMT

I also have had this problem...From what I've learned it seems to be a
problem w/ report parameters being out of order when depending on one
another...

try changing around the order of the parameters...

Cheers!
Ben Sullins

> I'll try to find a report of mine that does this and see if it still does it
> in RS 2005.
[quoted text clipped - 31 lines]
> >>> Thanks,
> >>> Chris McKenzie

Reply to this Message

Chris McKenzie - 22 Sep 2005 19:06 GMT

I don't have any dependencies between report parameters. That's a good idea
though.

Chris

>I also have had this problem...From what I've learned it seems to be a
> problem w/ report parameters being out of order when depending on one
[quoted text clipped - 51 lines]
>> >>> Thanks,
>> >>> Chris McKenzie

Reply to this Message

gary - 30 Sep 2005 15:45 GMT

Any more ideas? This is causing me a ton of grief. I have multiple
parameters that depend on the previous parameter or parameters and can
not get it to work no matter what order of parameters I use.

Gary

> I don't have any dependencies between report parameters. That's a good idea
> though.
[quoted text clipped - 64 lines]
> >> >>> Thanks,
> >> >>> Chris McKenzie

Reply to this Message

gary - 30 Sep 2005 15:47 GMT

> I don't have any dependencies between report parameters. That's a good idea
> though.
[quoted text clipped - 64 lines]
> >> >>> Thanks,
> >> >>> Chris McKenzie

Reply to this Message