A script-enabled browser is required for this page to function properly.

Page Protect property

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

 

Yes

If the contents of the object cannot fit on the current logical page, the object and all of its contents will be moved to the next logical page.

For a repeating frame, the first instance of the repeating frame must be able to fit on the same logical page. Otherwise, the Page Protect condition is not satisfied. For any layout object other than a repeating frame, Yes means the object must be able to format entirely on the same logical page.

No

Object may be split across subsequent logical pages

Required/Optional

 Optional

Default

 No

 Restrictions

graphic depicting situation described above

Examples

Example 1: Small object

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.

Page Protect property set to No, as described above

 

Page Protect property set to Yes

Example 2: Large object

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.

Example 3:  Group report

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.

Example 4

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 department’s 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.

graphical depiction