I have a Documents.Report that I'm trying to print in 4 equal quadrants on a page. What I've done is to get the page width and height and divide each by 2 to get the height of the 2 rows of a table and the width of the 2 cells within each row. Those values are then used to place text and images within the various cells of the report.
This seems to work properly and did work properly in Version 7.3 but with 8.1 I'm having problems. It appears as though the document is always being generated with a 1" top and 1" left margin pushing everything down and right.
I've tried setting everything that I can find to 0's (Section.PageMargins, etc.) but nothing seems to make any difference. I've also tried setting the report Preferences FitToMargins to false (and true), again no difference.
Anyone have a clue as to how to get something to work without these margins (or at a minimum, a margin that is the "PageSettings.HardMarginX/Y" values.
Any help would be appreciated as I was very close to being done before 8.1 and now, not.
Neil
Actually, my issue is a bit worse (I think). What I do is print the report to a PDF and open the PDF for review. The PDF file is displayed with the1" top and left margin for some reason but if you then print from the acrobat reader/preview it prints almost properly.
So, my "revised" statement of the problem is ... why would the generated/previewed PDF file look so much different when previewed and then printed.
The user won't actually print the document since it looks so bad during preview.
Neil,
I'm not sure what your problem could be here. There were very few changes made to the Documents assembly for 8.1, and none of them appear to have anything to do with what you say you are doing. I also can't say why a report would look different when previewed vs printed, since I think this is more an aspect of how the PDF reader interprets the file after it's been written out. I would recommend that you submit a sample to the support group so that they can look into it; perhaps there's a seemingly innocuous code somewhere that is causing this problem.
Get Help
-Matt
Sorry for wasting your time.