Someone please help me with a workaround on this issue:
I have created three reports: (ReportA, ReportB and ReportC).
ReportA includes a subreport (ReportB). ReportB consists of one list. The list is bound to a dataset. The list consists of one subreport (ReportC). ReportC is an empty report.
What is the problem:
When running Report A,The report generation fails when the dataset that is used in ReportB returns zero rows and the report is rendered across two or more pages.
The same problem also occurs when the dataset returns one or more rows and every row are filtered away using a filter expression on the list in ReportB
To make sure that the report is rendered across two or more pages, just add some dummy data to reportA.
When reportB is run, the problem does not occur.
The first page is genereted correctly, but when I navigate to the second page, the error occur.
Anyone experienced the same issue?
This sounds similar to something I am experiencing. I am using SQL 2005.
I have 5 levels of nested reports.
The first page always displays as expected.|||Microsoft has confirmed to me that this issue is a bug and that this should be solved in Service Pack 1.|||
Wow, that's great.
My PM actually solved this on for us with a work around. It's a problem related to a common business issue "asymetrical heirarchy". If there is no data in the 3rd level, it affects the turn down control on the top level. We are currently re-writing our queries to always produce results, and then hide the display when the childID = parentID.
Microsoft SRS 2005 already handles this issue better than most others, but if they're going to fix it all the way, that's great!
|||Hello,
when RS2005 SP1 wil be released?
Thanks in adavnce
sql
No comments:
Post a Comment