Charles Rosecrans, Jr.
Top achievements
Rank 2
Rank 2
Charles Rosecrans, Jr.
asked on 12 Apr 2011, 12:03 AM
Forgive me for adding another "blank pages" item to the support log but I think I have a different example of when this happens from what I'm seeing.
This is in Q1 2011 that I'm seeing this.
I have a table of items which could take more than 1 page to print out. When I have more than 1 page worth of columns and I print the report by itself, everything works nicely. When I embed the report as a subreport in another master report, as long as it's the only subreport, it prints OK. When I embed a second subreport on the same master report, it starts printing 1 blank page for every extra page the table prints to (i.e, if the table needs 2 pages to print, it puts 1 blank page at the end of the master report, if it needs 3 pages, there are 2 blank pages at the end of the report).
I can make each report invisible and the report draws without any blank pages but as soon as the table is visible with any other subreport, it adds blank pages.
I thought I could get around this by using the ReportBook class to just combine multiple reports together, but the blank pages then become the table sub report and which ever report is second.
I have used the suggestions for finding which subreport could be flowing onto extra pages but the only thing it tells me is the detail section for the master report (where my subreports live) is flowing onto the blank last pages.
It looks like having multiple subreports in the detail section, 1 of which could maybe flow to multiple pages, causes some problems for planning how to draw each page.
Is there any way to correct this or figure out what I might be doing to cause the reporting engine to work this way?
Thanks in advance!
This is in Q1 2011 that I'm seeing this.
I have a table of items which could take more than 1 page to print out. When I have more than 1 page worth of columns and I print the report by itself, everything works nicely. When I embed the report as a subreport in another master report, as long as it's the only subreport, it prints OK. When I embed a second subreport on the same master report, it starts printing 1 blank page for every extra page the table prints to (i.e, if the table needs 2 pages to print, it puts 1 blank page at the end of the master report, if it needs 3 pages, there are 2 blank pages at the end of the report).
I can make each report invisible and the report draws without any blank pages but as soon as the table is visible with any other subreport, it adds blank pages.
I thought I could get around this by using the ReportBook class to just combine multiple reports together, but the blank pages then become the table sub report and which ever report is second.
I have used the suggestions for finding which subreport could be flowing onto extra pages but the only thing it tells me is the detail section for the master report (where my subreports live) is flowing onto the blank last pages.
It looks like having multiple subreports in the detail section, 1 of which could maybe flow to multiple pages, causes some problems for planning how to draw each page.
Is there any way to correct this or figure out what I might be doing to cause the reporting engine to work this way?
Thanks in advance!
3 Answers, 1 is accepted
0
Charles Rosecrans, Jr.
Top achievements
Rank 2
Rank 2
answered on 12 Apr 2011, 10:26 PM
I believe I have figured out what is going on and am a little embarrassed I didn't see it before.
It appears that a crosstab or table that spans multiple pages simply makes the PDF export wider, rather than simply fitting what it can on page #1, the fitting as much of the rest on page #2, etc.
Instead of formatting each page keeping the width of the page, it appears to push the crosstab out as far as it can, splitting it to fit on a page. This however, appears to make the page for the 2nd subreport also expand out to match the width of the crosstab and thus putting blank pages at the end of the document.
Maybe an example picture would describe what I think is going on best:
It appears that a crosstab or table that spans multiple pages simply makes the PDF export wider, rather than simply fitting what it can on page #1, the fitting as much of the rest on page #2, etc.
Instead of formatting each page keeping the width of the page, it appears to push the crosstab out as far as it can, splitting it to fit on a page. This however, appears to make the page for the 2nd subreport also expand out to match the width of the crosstab and thus putting blank pages at the end of the document.
Maybe an example picture would describe what I think is going on best:
0
Accepted
Hello Charles Rosecrans, Jr.,
Base on the description it seems that your subreport contains a report that is too wide, and while at design-time that is not obvious, at run-time it might cause the carry over to occur. Another option is if you have a Crosstab Column group thus your report is growing to right and expands the report sections width. If this is the case you can change the report's orientation to landscape provide enough space for the Crosstab to grow horizontally.
For additional information check out the Problem: Telerik Reporting renders blank pages KB article.
If you still experience any difficulties we will appreciate if you send us the problematic reports to examine in detail locally.
All the best,
Peter
the Telerik team
Base on the description it seems that your subreport contains a report that is too wide, and while at design-time that is not obvious, at run-time it might cause the carry over to occur. Another option is if you have a Crosstab Column group thus your report is growing to right and expands the report sections width. If this is the case you can change the report's orientation to landscape provide enough space for the Crosstab to grow horizontally.
For additional information check out the Problem: Telerik Reporting renders blank pages KB article.
If you still experience any difficulties we will appreciate if you send us the problematic reports to examine in detail locally.
All the best,
Peter
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Charles Rosecrans, Jr.
Top achievements
Rank 2
Rank 2
answered on 16 Apr 2011, 03:13 AM
Yes, the crosstab was flowing over on to multiple pages. I just thought that the rendering engine would print 1 page with as many columns as possible and then print the next page with as many, etc until it was done and then print the graph at the end. I didn't think each slice of the crosstab was widening the actual report page width. But it looks like the actual width is all columns layed out and the virtual page is what is printed.
Since my report is landscape only and some of the items we'd print push out to 10 and 12 pages of columns in the crosstab, I decided to use the report book and just feed it portions of the data set so it would only print one page for each crosstab report. It works just perfect now.
It was just helpful for me to understand that and after I did, what was going on made perfect sense.
Thanks for the reply.
Since my report is landscape only and some of the items we'd print push out to 10 and 12 pages of columns in the crosstab, I decided to use the report book and just feed it portions of the data set so it would only print one page for each crosstab report. It works just perfect now.
It was just helpful for me to understand that and after I did, what was going on made perfect sense.
Thanks for the reply.