This sample db demonstrates custom setting of maximum number of rows per page for one or more subreports.

    Setting of forced page breaks in subreport's detail section, though effective, suffers from the drawback that the subreport control on parent report gets forced to full page height. As a result blank space on main report goes waste. Though not recommended, this method has been demonstrated as the last option, just for academic interest.

    Note: 
    While using forced page break in subreport, it has to be ensured that CanGrow property of subreport control on parent report is set to Yes. Otherwise the subreport does not get displayed beyond first page. In fact what happens is that as a result of forced page break, the subreport control with CanGrow as Yes, expands suitably so as to span multiple pages as needed.    

    Following styles are demonstrated in the sample db:
    1 - A1: Single SubReport Style 1:
         The desired effect is achieved by conditional cancellation of detail format of subreport for records not falling in the target block determined by parent report's current record number. It is like obtaining a filtered output matching target block of sequential numbers. The number of pages on parent report is restricted to the minimum required for the subreport.

    2 - A2: Single SubReport Style 2:
         Similar to A1. However, the number of pages on parent report is not restricted. It can exceed the minimum required for the subreport.

    3 - B1: Two SubReports Style 1:
         Similar to A1 above, but with two subreports, each with its own setting for max rows per page.

    4 - B2: Two SubReports Style 2:
         Similar to A2 above, but with two subreports, each with its own setting for max rows per page.

    5 - C: Single SubReport With Forced Page Break:
         Not recommended. Included for academic interest only.