Telerik
Home / Support / Knowledge Base / Telerik Reporting / General, Installation / Problem: Telerik Reporting renders blank pages

Problem: Telerik Reporting renders blank pages

Article Info

Rating: 3

Article information

Article relates to

Telerik Reporting, all versions

Created by

Rossen, Telerik

Last modified

Aug. 10, 2007

Last modified by

Rossen, Telerik

 
PROBLEM

After designing a report in VS2005, some of the pages render as blank, both in the WebViewer or the WinViewer.

DESCRIPTION
The pages are not actually blank. Rather there is some content that cannot fit on the current page and is carried over to the next page. There are several cases when this happens:

  • Report Width is greater than than the available page space (Page Width - Left Margin - Right Margin).
  • There is a sub-report, which 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.
  • There is a report item with boundaries going out to the right from its parent section.
Since often the background color (white in most cases) of the item that is carried over to the next page is the same as the background of the report/sections the page seems to be blank.

SOLUTION
To see which items are causing the problem, simply change their background to a different, more contrasting color and run the report in the WinForms viewer or export it to PDF. The rendered report will immediately give you a clue about the items which are at fault. Then simply try making the report items smaller until the "blank" pages disappear or decrease the report width. We would advise creating the items so that they do not touch other items, section ends, etc., because the processing engine might produce unexpected results. Always leave a little space (a couple of pixels/points) around report items to prevent unexpected behavior.

Blank pages at the beginning of the HTML report can appear, because the DetailSection has its KeepTogether property set to true and the HTML rendering engine attempts to render it on a single page (it is later that it "realizes" that this is impossible). Since the first page contains the ReportHeader, the rendering engine tries to render the detail on the second page, which has more available space. In light of this, try setting the KeepTogether property of the DetailSection to false and/or delete the ReportHeader section of the report, if you do not need it.

Comments

There are no comments yet.
If you'd like to comment on this KB article, please, send us a Support Ticket.
Thank you!

Please Sign In to rate this article.

Powered by Sitefinity ASP.NET CMS

Contact Us | Site Feedback | Terms of Use | Privacy Policy
Copyright © 2002-2010 Telerik. All rights reserved.