Jeremy Radosh
Top achievements
Rank 1
Rank 1
Jeremy Radosh
asked on 09 Sep 2008, 01:28 PM
I have a simple report with a Page Header section and a Detail section. The report shows only one row of data, however there is a LOT of text data to display. There are approximately 7 text boxes in the detail section, and each might have a few paragraphs of text. On average the text will span 3 or 4 pages (8.5 x 11) when printed.
The problem I'm having is that the report is rendered as one long page with a single header/footer instead of 3 or 4 separate pages each with its own header/footer.
How can I get the report to render a page header/footer for each printed page?
Thanks
Jeremy
The problem I'm having is that the report is rendered as one long page with a single header/footer instead of 3 or 4 separate pages each with its own header/footer.
How can I get the report to render a page header/footer for each printed page?
Thanks
Jeremy
1 Answer, 1 is accepted
0
Hi Jeremy,
Generally such approach is wrong and not intended for our reporting engine. You're basically stretching a single detail section and it forcibly creates new pages for you - this is how creating a document would work like. Instead our Reporting let's you specify datasource and like standard repeater creates multiple details section based on your row count. This way it handles the creation of the pages for you and makes sure a proper layout is in place. On the contrary with the "document type" approach you're using, it forcibly creates pages, by placing n items, checking where does the previous item end and where should the new start and constantly recalculating how many items would fit on the current one. This along with the fact that HTML is not a page oriented format, causes the problem you've encountered.
If you want multiple pages, you should split your content into multiple datarows, so that this can be handled gracefully or accept this fact and ignore it. It should still be exported properly to multiple pages in PDF, RTF and TIFF formats.
Greetings,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Generally such approach is wrong and not intended for our reporting engine. You're basically stretching a single detail section and it forcibly creates new pages for you - this is how creating a document would work like. Instead our Reporting let's you specify datasource and like standard repeater creates multiple details section based on your row count. This way it handles the creation of the pages for you and makes sure a proper layout is in place. On the contrary with the "document type" approach you're using, it forcibly creates pages, by placing n items, checking where does the previous item end and where should the new start and constantly recalculating how many items would fit on the current one. This along with the fact that HTML is not a page oriented format, causes the problem you've encountered.
If you want multiple pages, you should split your content into multiple datarows, so that this can be handled gracefully or accept this fact and ignore it. It should still be exported properly to multiple pages in PDF, RTF and TIFF formats.
Greetings,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.