The Page Protect property specifies whether to try to keep the entire object and its contents on the same logical page.
Note: Using Page Protect may cause objects below the page protected object(s) to appear above the page protected object(s).
Applies to |
Layout objects | ||||
Values |
| ||||
Required/Optional |
Optional | ||||
Default |
No |
Page Protect applies only to the first logical page on which the object is triggered to be formatted. Page Protect is ignored on subsequent pages.
For repeating frames, Page Protect refers to each instance of the repeating frame. Each instance of the repeating frame and its enclosed objects will be kept together by Page Protect. The only exception is that page protection is not applied to the first instance on a page other than the first page of the repeating frame. For example, in the diagram below, page protection is applied to instances 1, 2, and 4, but not to instance 3. Instance 3 is the first instance to format on the second page of the repeating frame. Notice that, in this case, if page protection had been applied to instance 3, it would have started on page 3 instead of page 2. This would have left page 2 almost completely blank.
Page Protect is not supported for repeating frames that are part of a matrix. When repeating frames are related through matrix object, setting Page Protect will not affect them.
If moving the object and its contents to the next logical page would leave the current logical page blank or only containing repeated objects (for example, a page heading), Page Protect will not be applied. This prevents unnecessary blank pages in your report.
If Page Protect causes an object to be moved to the next logical page when formatting, an object alongside the page protected object may or may not be moved as well. If the object alongside the page protected object is not anchored (implicitly or explicitly) to the page protected object, and that object can fit in the space where the page protected object could not fit, the object will print on that logical page. Otherwise, the object will be moved along with the page protected object to the next logical page.
Suppose that you have created a frame named M_1 with a number of fields that display various columns and summaries. For ease of reading, you want to keep all of the fields in M_1 on the same logical page so that readers can see the columns and their summaries together.
Specify Page Protect for M_1. If M_1 and all its fields cannot fit on the first logical page that Reports Builder attempts to print them, Report Builder will try to print M_1 and all its objects on the next logical page.
Suppose that you have created a frame named M_1 with a number of fields that display various columns and summaries. For ease of reading, you want to keep all of the fields in M_1 on the same logical page so that readers can see the columns and their summaries together.
Specify Page Protect for M_1. If M_1 and all its fields cannot fit on the first logical page that Reports Builder attempts to print them, Reports Builder will try to print M_1 and all its objects on the next logical page.
Suppose further, though, that M_1 and all its fields cannot fit on the second logical page on which Reports Builder tries to print it. Reports Builder will print as much of M_1 as it can on the logical page and print the rest of it on the following logical page.
Suppose that you have a group report. If at all possible, you would like to have all of the details and the master appearing on the same page. To do this, you specify Page Protect for the master repeating frame (the outermost repeating frame). If the details and the master cannot fit on the first page on which they are triggered to print, they will be triggered to print on the next page instead.
Assume you are designing a group report made up of department
numbers and employees, as shown below. Without Page Protect set on
for a repeating frame, a departments employee names could split
between pages. Specifying Page Protect for the repeating frame that encloses
the Deptno field ensures that the department number and all of its related records
will always appear on the same page.
Copyright © 1984, 2005, Oracle. All rights reserved.