March 21, 2011 at 1:44 pm
Hello,
I am using SQL Server Reporting Services R2.
I have created a report using SQL Server BI Development Studio:
1) I've gone into report properties - page set up
2) I've set the orientation to portrait
3) The width is 8.5 in.
4) The length is 11 in.
5) The size is set to letter
6) I've set the left margin to .25 in.
7) I've set the top, bottom and right margin to .50 in.
8) I've moved the textboxes with the date and total pages count (X of Y) to above the above the body.
9) The body size is 11.76042 in, 1.79792 in.
10) The first printable Column is at 4.5 in. (The first three grouping columns are hidden.)
Everything looks great in the browser. The toolbar in the browser says I have 41 pages.
When I go to print it, there is 63 pages. Of course, the manager is screaming about this.
I might add that I never had this problem when printing from Crystal Reports. In other words, the printer is the same. Same Server. Same print configurations.
I'm still making the conversion from Crystal Reports to SSRS.
Question
======
I'm not sure, when using SSRS, how to insure that the number of pages that you see in the browser is the number of pages that print out.
I'd appreciate it if someone could point me in the right direction.
Thanks,
Tony
Things will work out. Get back up, change some parameters and recode.
March 24, 2011 at 4:23 am
WebTechie38 (3/21/2011)
Everything looks great in the browser. The toolbar in the browser says I have 41 pages. When I go to print it, there is 63 pages. Of course, the manager is screaming about this.
If you view it in the designer page preview (not the HTML view) and also export to PDF, it comes out at 41 pages? If you print the PDF in Adobe Reader, still 41 pages or something else?
I had an issue similar to that which was caused by HP PCL 6 printer drivers; swapping for PCL 5 ones fixed it (or was it from switching from the Universal driver to a model specific one... something like that anyway).
But if it's right, is the problem when you export it from an actual web browser on the server as PDF?
I've had an issue where the PDF from the designer was fine, and PDF from the web browser on the production server was different and longer. The reason was because I was using some standard font (I think it must have come from Office) that was on my workstation but was being substituted on the Server OS that didn't have it for a bigger font, and thus more pages.
March 24, 2011 at 5:31 am
Actually, if I just print preview, the total pages says 63.
When viewing the report in Report Manager, the tool bar says 41.
If I print to pdf or just print preview, the total number of pages changes from what I see in Report Manager.
Thanks,
Tony
Things will work out. Get back up, change some parameters and recode.
March 25, 2011 at 6:34 am
I see from searching the internet that I am not the only one to notice this particular behaviour of SSRS.
Though I am getting more and more proficient at creating reports in SSRS (and have started taking on clients with that new skill), I have to say that I still think Crystal Reports is better and easier.
It is probably something to do with the difference between the interactive page width and the report page width. From my internet studies, I think, what we see in Report Manager is the interactive page width. When we go to print a page or send it to a pdf, it has to calculate the page width minus margins.
This would account for the difference in pagination from what we see in Report Manager to what is actually printed.
Things will work out. Get back up, change some parameters and recode.
March 25, 2011 at 7:09 am
Have you checked the InteractiveSize on the Report Properties as compared to the PageSize Property of the Report (not the body object).
March 25, 2011 at 11:40 am
WebTechie38 (3/21/2011)
Hello,I am using SQL Server Reporting Services R2.
I have created a report using SQL Server BI Development Studio:
1) I've gone into report properties - page set up
2) I've set the orientation to portrait
3) The width is 8.5 in.
4) The length is 11 in.
...
9) The body size is 11.76042 in, 1.79792 in.
I'd appreciate it if someone could point me in the right direction.
Thanks,
Tony
Do some of the pages come out blank when the report is rendered for printing? One dimension of the body size you gave (11.76042 in) exceeds both dimensions of the page size (8.5 in x 11 in). When SSRS renders a report for printing, it includes the entire body of the report, not just areas with report items present. If a dimension of the body size of your report exceeds the corresponding "printable" dimension (page diminesion minus margins), SSRS has to extend the body to another page. I suspect that this is happening with your report. Try fitting the body to the page size and see if you get better results.
Jason Wolfkill
March 25, 2011 at 12:08 pm
Hello,
Yes, I went back and forth to make sure the columns were more narrow. I saw blank pages and took care of that.
But even after all that the display page count is 41 pages. The printed page count is 50 pages.
I think the display page count is based on one page width (interactive page width).
I think the printed page is based on a different page width (report page width).
I think that is why I have a different pagination count going on.
I could be wrong.
Thanks for responding! It is really appreciated.
I would say I am at an expert or close to expert level with Crystal Reports. I am quickly getting up to speed with SSRS. Issues such as this are really helping me to get to know the product. So I thank you for giving me your ideas.
Tony
Things will work out. Get back up, change some parameters and recode.
March 25, 2011 at 12:17 pm
You are absolutely right about the "interactive page width" and the "page width" settings. As has been noted elsewhere, you may need to tweak the "interactive page width" dimensions to equal the "printable page" dimensions (i.e., page dimensions minus margins) to get the displayed page count and the printed page count to be the same. Even then, it may not work every time because the different rendering extensions used to display and print reports may have their own quirks that are hard to anticipate.
Jason Wolfkill
March 25, 2011 at 8:06 pm
wolfkillj (3/25/2011)
As has been noted elsewhere, you may need to tweak the "interactive page width" dimensions to equal the "printable page" dimensions (i.e., page dimensions minus margins)
I set my templates to that by default, I assumed everyone else did the same ...
Even then, it may not work every time because the different rendering extensions used to display and print reports may have their own quirks that are hard to anticipate.
I've had very, very few problems with a proper interactive=page=report+margins setup.
March 26, 2011 at 7:11 am
I never knew about an interactive page width until the client started complaining about seeing one page count in the tool bar and another when they printed out the pages.
To be honest, I have not created templates yet. I have a report that I used to copy to get me started with all reports. It has the color and all that I need. It is a quasi template.
But thanks for the suggestion. I will create some templates with the interactive page width set.
Now, I think everyone is saying:
Interactive page width = Report Page width - left margin - right margin
Interactive page height = Report Page height - top margin - bottom margin
I will give that a try.
Thanks,
Tony
Things will work out. Get back up, change some parameters and recode.
March 27, 2011 at 7:28 pm
If you use headers or footers, you also need to subtract those heights from the interactive size in order to get the page count to match. I just tried it (RS 2008).
I haven't used Crystal Reports (I have used ActiveReports though), but as annoying as some SSRS things are, it'll really grow on you if you let it.
March 30, 2011 at 9:55 am
I've written a python script which can recalculate and rewrite the interactive sizes on any reports you have:
http://www.ssrstips.com/tool-to-calculate-interactiveheight-and-interactivewidth
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply