Whether or not you're using subreports, if you have page spillover and your body design fits within the margins of the page, look for something allowed to grow that pushes the width of the body out. I could eliminate my problem by increasing colspan where the subreport was placed.

Access creates the form and displays it in. Then, after changing some other column widths (and without exceeding the body width plus margins), the winform and browser renderings looked still looked fine but when the output (printer or pdf) was generated, it grew past the margins and wrote the right side of each page as a 2nd (4th, etc.) page. On the Create tab, in the Forms group, click More Forms, and then click Datasheet. It looked like the span could contain it in the designer and it rendered fine in a winform or a browser and, originally, it could generate printer output (or pdf file) without spilling over onto excess pages. I had a similar problem arise with a subreport that could be placed in a cell (spanning 2 columns). If your report includes a subreport, the width of the subreport could push the boundaries of the body if subreport and hierarchy are allowed to grow. The fastest way to add grouping, sorting, or totals to a desktop database report is to right-click the field to which you want to apply the group, sort, or. So one will need to make the size of the controls smaller to accommodate a smaller page size.Īlso in some circumstances one can just change a property of the report page by setting ConsumeContainerWhitespace to true to automatically consume the spaces. If #3 does not resolve the issue, then there are controls requiring too much of the actual page size and going over in either length/width.Then try to create a PDF and see if that fixes it.Visually look at the width/height and see if you can't bring in the page on the design surface to size it to the space actually needed by the controls and no more.

In the design surface, sometimes the editor will create a page which is larger than the actual controls hence the ghost area being printed.

It is better to do this on the design surface ( Visual Studio 2012 is shown but can be done in other versions) first before calculating any maths when editing an SSRS document.īelow the following numbers in red circles that map to these following steps:

Microsoft access tabular layout