Bug?-when using nested subreports in combination with list

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

Bug?-when using nested subreports in combination with list

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

Bug?-when using nested subreports in combination with list

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

Border problem with subreports containing tables

I have written a main report that, for the sake of modularity,
consists of several subreports that can be switched in and out. The
main report and subreports do not include borders as part of their
internal properties. When adding each subreport item to the main
report I have applied left and right borders to that subreport item's
properties. The reason I have not applied the borders to the main
report is that I only want borders on the subreports.
The problem I am having occurs when a subreport consists only of a
table. In such cases, the borders are only rendering for the height
of the table, i.e. if a table is only half a page high then the
borders are only half the page height, whereas I want the borders to
take up the entire page height. I can get around this by defining the
height of the subreport to match the height of the main report, which
forces the borders to be excatly the defined height. However, this
has the unwanted side-effect (bug?) of adding a blank page (with
borders) to the main report inmmediately after the subreport.
If anyone has any ideas for how to achieve page height borders in this
scenario I would be very grateful to hear them.Increasing the height of the subreport will give you blank pages, the
height should be kept min ( abt .115 in), what happens is subreport
will expand to accomodate the data.
what border are you referring to? the border of the subreport table?
do u want like a sqare border for each subreports you include in the
main report?
Couldnt really understand your question.
let me know in detail..maybe i can help.
Regards,
Amit Bhandari.
jcbpalmerpcdev@.yahoo.co.uk (Julian) wrote in message news:<7a53e044.0410271336.4df0aa97@.posting.google.com>...
> I have written a main report that, for the sake of modularity,
> consists of several subreports that can be switched in and out. The
> main report and subreports do not include borders as part of their
> internal properties. When adding each subreport item to the main
> report I have applied left and right borders to that subreport item's
> properties. The reason I have not applied the borders to the main
> report is that I only want borders on the subreports.
> The problem I am having occurs when a subreport consists only of a
> table. In such cases, the borders are only rendering for the height
> of the table, i.e. if a table is only half a page high then the
> borders are only half the page height, whereas I want the borders to
> take up the entire page height. I can get around this by defining the
> height of the subreport to match the height of the main report, which
> forces the borders to be excatly the defined height. However, this
> has the unwanted side-effect (bug?) of adding a blank page (with
> borders) to the main report inmmediately after the subreport.
> If anyone has any ideas for how to achieve page height borders in this
> scenario I would be very grateful to hear them.