The Page Break After property specifies that you want all children of the object to be moved to the next page. In other words, any object that is a child object of an anchor (implicit or explicit) to this object will be treated as if it has Page Break Before set to Yes. Note that this does not necessarily mean that all the objects below the object with Page Break After will move to the next page.
Applies to |
Layout objects |
Values |
No |
Required/Optional |
Optional |
In the diagram below, Page Break After is set to Yes for frame M_Dept. Both M_Dept and M_Emp have Fixed Vertical and Horizontal Elasticity. Page Break After does nothing in this case because M_Dept and M_Emp are siblings inside of the parent frame M_Parent.
In the diagram below, everything is the same as the previous case except that M_Dept is explicitly anchored to M_Emp as the parent. Page Break After delays the formatting of M_Emp in this case because M_Dept is the parent of M_Emp.
In the diagram below, notice how B_Graph, which appears below R_Sal in the layout, actually ends up printing on page 1 with R_Sal. This happens because B_Graph is not a child of R_Sal. If you explicitly anchored B_Graph as a child to R_Sal, then B_Graph would have appeared on page 2 instead of page 1.
Suppose that you want each instance of a repeating frame to be on a logical page by itself. First, set Maximum Records Per Page to 1 for the repeating frame so that only one instance appears on each logical page. Then, specify Page Break Before and Page Break After, to make sure that the first instance of the repeating frame starts on a new logical page.
Copyright © 1984, 2005, Oracle. All rights reserved.