I'm getting some extra pages when I export to Word.
I was getting this previously when an item exceeded the width of the page, but I cannot identify this as the existing problem.
When I change the background color of items to see if any exceed the page width, it appears that the item may calculate too wide, but renders within the page width so the finished rendered product is correct, but the extra page break has already been triggered.
I have a bunch of tables that are stacked (about 12) and some do not render because they lack content on specific loop iterations.
I apply a post init cleanup that re-stacks the tables so that they are right on top off each other but stepped by a couple pixels so they will display properly by auto growing without extra white space when a table isn't rendered.
This issue does not happen when exporting to PDF, RTF or when I change the page width, but the vertical padding is different so I'm assuming its how the Height is calculated from the Auto Grow.
I was getting this previously when an item exceeded the width of the page, but I cannot identify this as the existing problem.
When I change the background color of items to see if any exceed the page width, it appears that the item may calculate too wide, but renders within the page width so the finished rendered product is correct, but the extra page break has already been triggered.
I have a bunch of tables that are stacked (about 12) and some do not render because they lack content on specific loop iterations.
I apply a post init cleanup that re-stacks the tables so that they are right on top off each other but stepped by a couple pixels so they will display properly by auto growing without extra white space when a table isn't rendered.
This issue does not happen when exporting to PDF, RTF or when I change the page width, but the vertical padding is different so I'm assuming its how the Height is calculated from the Auto Grow.
2 Answers, 1 is accepted
0
Hi Steven,
Petio Petkov
the Telerik team
You should note that Microsoft Word does not support the concept of hard pages. Instead, when the exported document is opened in Word, Word re-paginates it again based on the page size (source: Design Considerations for Word Rendering). This might cause some misalignments when the report size is very close to the page size. If you need further assistance with the report, please open a support ticket and send us the report definition. This way we will be able to review it locally and give you more adequate advice.
Regards,Petio Petkov
the Telerik team
Have you tried the new visualization options in Telerik Reporting Q1 2013? You can get them from your account.
0
Steven
Top achievements
Rank 1
Rank 1
answered on 05 Apr 2013, 02:28 AM
It ended up being a top/bottom padding issue.
Word was calculating the padding a bit different and this pushed the content to exceed the page height.
What I had to do was take the WinForm version and the exported word version side by side at 500% zoom to identify what element padding was causing me trouble. I tweaked the troublesome items and then page size outputted correctly.
Thanks
Steve
Word was calculating the padding a bit different and this pushed the content to exceed the page height.
What I had to do was take the WinForm version and the exported word version side by side at 500% zoom to identify what element padding was causing me trouble. I tweaked the troublesome items and then page size outputted correctly.
Thanks
Steve