In a Page report (.rdlx) layout, you can create very specific styles of reports that are very difficult, if not impossible, in other .NET reporting tools. You design this type of report on a page where none of the report controls can grow or shrink at run time, making it ideal for duplicating legacy paper forms. This report type is great for billing statements, mail merge, catalogs, forms, and other reports with layout constrictions.
Page report controls do not change in size based on the data, but you can use an Overflow Place Holder to handle any extra data.
With Page reports, there is no need to use code or add measurements to make sure that everything fits. Unlike the RDLX report, the controls remain fixed at run time, so you can drop a table on the report, set a property to size it exactly how you want it, and have something very close to a WYSIWYG report at design time.
You can set page level grouping to render one row of data on each page. This is ideal for something like a tax form that you want to print for every client or every employee, or an invoice that you want to print for every customer.
If there is data that does not fit within the space allocated for the data region at design time, you can assign it to flow into an OverflowPlaceholder control. This can go on the same page in a different area, for example, in the form of columns, or it can go on a separate page.
You can add multiple themes to a report. In this case, the report renders a combination of multiple outputs for each theme. For example, if a report has two themes, then the report output includes a combination of the first and the second themes, applied to each report page. You can control the combination rules of the report output in the CollateBy property.
In a Page Report, you can set the basic properties for your page from the FixedPage dialog. You can access the FixedPage dialog by doing one of the following: