Ok, for the life of me I can't seem to get this to work. Whenever I used the client-side print for SRS2000 SP2 it will always print out a blank page at the end.
At first I thought it was the margins, because not matter what I did the right-most column would always get chopped off. It would preview and look great, but as soon as I printed the page the last column would be chopped in half and print on a separate page.
So to troubleshoot I created a table that had only one column that was placed in the center of the page (using padding). Event after doing this the column STILL got chopped in half and printed out in two pages. Yet previewed and looked like it would print out ok.
Any help would be greatly appreciated. This one is driving me crazy.
Ok scratch this one. Turns out I wasn't accounting for the margins that were being set somewere. Once I reduced the body and table width by .1 inch then the right hand column isn't chopped and the correct number of pages prints out (no blanks).
There report has no margin and when printing I was sure to set the margins to 0 there as well.
Anyone tell me where this margin is coming from? Is this printer specific?
Thanks
|||
Have you tried to go to REPORT PROPERTIES for the specific report?
and establish the width in CM or inches?
Did you also look at report headers and footers
How large is your "print frame"
Are you using RS 2000 or RS 2005?
Can Help u!
|||
RS 2000.
The body of the report is 8.5" x 11". In the report properties->layout the page width is also 8.5" x 11". In the same section all margins are set to 0. My table is the entire width of the body (i.e. also 8.5" wide).
Now when I print the report using the Active X client side print component there is a margin added to the report that I hadn't accounted for. This margin was chopping the right column off and having it print on a separate page. This margin exists even though no margins are set for the report and when printing there are no margins set there as well.
What had been confusing me was that no matter how wide I made the table it still printed two pages. What I didn't realize is that I had to reduce the width of the body as well.
So by setting the width of the body to 8.45" and the width of the table to the same 8.45" the report prints on one page as expected.
Now, that we are on the same page, where did this margin come from knowing that I did not set it anywhere? The printer, RS2000, the client side Active X control...?
Thanks
|||Hi,
I rather experience a very peculiar problem. I have developed a page in asp.net, which has a Print button by itself. It has to take the user to the printer window (I have used window.print()). When the user selects the printer and says print the first and the third page ( third page being the last page) gets printed properly where as the second page will have problems with the right side margin. This page is getting created on the run depending on the user's inputs. When I view the print preview, I found that the text in the next line of the page also comes to the previous page resulting in the loss of datain the II page content alone.
For example,
In the actual page, if I have
When a page from the web is printed, sometimes the right
hand side centremeter will be cut off.
Microsoft has a knowledge base article about this problem:
The text in the print preview would be,
When a page from the web is printed, sometimes the right hand side centremeter will be cut off. Microsoft has a
knowledge base article about this problem:
therefore resulting in the loss of data. I have tried adjusting the right and left side margins, but without luck.
This happens even if i print it with/without back to back option.
Even if i ask for the II page alone to be printed twice instead of the whole web page content, both the pages have the right side margin lost.
The same content that appears in the II page if made to appear in the III page does not affect the right margin of the III page. Thus, it does not have any content related issues.
Printing with landscape option wont be a reasonable option for the user. So, that can be ruled out.
Please advise what could be the work around at teh earliest as i have to get back to the user.
No comments:
Post a Comment