Page break between subreports - how to?
Tom Jastrzebski
Wow do I enter a page break between two subreports? (SSRS 2005)
Tomasz
Wei Lu
Thank you for posting.
In Reporting Services 2005, Item page breaks apply only to the report items
rectangle, table, matrix, list, and chart.
So if you want to add a Page Break between 2 subreports, please add a
rectangle in the report and drag your first subreport into the rectangle.
Then in the Properties of rectangle, on the General tab, for Page breaks,
select Insert after rectangle. After that, you can add your second
subreport.
Hope this will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Tomasz Jastrzebski
I did what you adviced and put each subreport inside a Rectangle, and set
PageBreakAtEnd=True.
However, now SSRS 2005 does not paginate my report at all. Subreports run
separately are being paginated as expected.
Just placing them as subreports on the main report causes pagination to stop
working and everything, including eight subreports, renders in html as one
long page. Same when exported to Excel. Is there any report property I
missed?
Thank you,
Tomasz
Wei Lu
Thanks for the update.
It's weird. If your subreport contains some data and you have set the
PageBreakAtEnd property, it should work. Would you please check this issue
on another report with Page Break? You may create a report like this:
1. Create a report.
2. Add a rectangle, then add a textbox in the rectangle and another textbox
under the rectangle.
3. Enter some text in these two textboxes and set the PageBreakAtEnd=True.
4. Deploy this report to the report server and access it via web. Does this
issue appear?
Tomasz Jastrzebski
It looks like I identified the problem. If you change rectangle
Visibility.Hidden property value to some expression, let's say "=False"
instead of the default "False" the pagination set by the PageBreakAtEnd will
stop wok.
I would consider this a bug.
Thanks,
Tomasz
Wei Lu
Thank you for the feedback.
This is a known issue. Page breaks on report items with conditional
visibility are ignored. The current rendering architecture for some of the
renderers doesn't support it.
I was also confirmed that this issue will be fixed in the next version
after SQL Server 2005.
Sorry that we have no solid solution for you at this time. Appreciate your
understanding on it. Please let me know if I can be of further assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "Tomasz Jastrzebski" <oeg...@nospam.nospam>
>References: <ugHBpC3Y...@TK2MSFTNGP05.phx.gbl>
<vnscNa4...@TK2MSFTNGXA01.phx.gbl>
<O#V93VUa...@TK2MSFTNGP02.phx.gbl>
<BNJWJcca...@TK2MSFTNGXA01.phx.gbl>
>Subject: Re: Page break between subreports - how to?
>Date: Mon, 1 May 2006 11:49:18 -0500
>Lines: 12
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
>X-RFC2646: Format=Flowed; Original
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Message-ID: <OGIOy7Tb...@TK2MSFTNGP04.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.reportingsvcs
>NNTP-Posting-Host: 12.161.140.3
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:72970
>X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
Tomasz Jastrzebski
That is a pretty bad news. Especially because this bug also breaks
(disables) pagination in subreports.
I do not think it was a good idea to introduce this bugs in order to
maintain consistency between renderers.
It seems like pagination one of the weakest points of this version, and the
new one can be probably expected around 2010.
Thanks for the confirmation.
Tomasz
"Wei Lu" <we...@online.microsoft.com> wrote in message
news:tjAIBLb...@TK2MSFTNGXA01.phx.gbl...
Wei Lu
Thank you for your understanding. Unfortunately we could not provide solid
solution for you at this time.
If you have any questions or concerns, please feel free to let us know.