Report always needs printing, while printing always needs page break
A kind of common page break is automatic page break by paper size and page margins. Before printing or displaying, it will calculate that how many rows and columns can be displayed in each piece of paper according to page size and page margins. However, this mode is easy only when the height and width of rows and columns are fixed.

As data are dynamically fetched from database, if they exceed the width of cells, they will widen or heighten cells. Therefore, users have to fetch data and judge whether the data will exceed the width of cells first. Then, they can calculate that how many rows and columns can be displayed in each piece of paper.

Another kind is page break by fixed row number. It means that each piece of paper display fixed number of rows, and the remaining will be displayed in following pages. Users always use this mode for orderly format or preformatted paper printing.

For it needs not to do complex calculations, this mode seems easier. However, as users' requirements are various, data may exceed the width of cells. It means that the data have to wrap text without change the width and height of cells. Then, the only solution is to shrink font. Nevertheless, it is difficult. For best display effect, the final font is decided with complicated calculations according to both width and height of cells.

In addition, there is another problem about empty rows. As data are dynamically fetched from database, the number of rows is unfixed, and there may be empty rows in the last page. Therefore, users have to supplement these empty rows. Then, how many empty rows are there? It is difficult to know, and users have to do dynamic calculations according to practical condition.

There are more complex page break modes. For example, page break with automatic adaptation to paper size. This mode is usually used in reports with dynamically horizontal expansion. As users want to print report in a piece of paper without horizontal page break, and the column number is unfixed, it needs to adjust column width according to final column number.

To sum up, page break is important, and the page break modes provided by a reporting tool can influence the work efficiency of users greatly. In my opinion, RAQ Report is doing well in these aspects by providing a series of simple and useful modes.

After report design, users only need to select a page break mode and a zoom mode, and set related parameters like Rows per page, Print type of vertical break, Print type of table header and footer, etc.

This post is from freezea's blog. You are welcomed cc it anywhere, and please indicate the source.