Microsoft KB Archive/209667

= ACC2000: Explanation of the KeepTogether Property for Sections =

Article ID: 209667

Article Last Modified on 12/12/2002

-

APPLIES TO


 * Microsoft Access 2000 Standard Edition

-



This article was previously published under Q209667



Novice: Requires knowledge of the user interface on single-user computers.

This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).



SUMMARY
Form and report sections have a KeepTogether property that you can set to Yes or No. The KeepTogether property setting for sections determines whether Microsoft Access prints the controls located in that section on a single page or on more than one page.

The section's KeepTogether property affects the controls located in that section for a single record.



MORE INFORMATION
If the KeepTogether property is set to Yes, Access begins printing the controls located in that section at the top of the next page if it cannot print all of the controls on the current page. If it is set to No, Access prints as many controls as it can on the current page and continues printing them on the next page.

If all the controls in a section require more than one page for a single record, Access continues printing on a second page, regardless of the KeepTogether property setting.

For example, say the detail section of a report has its KeepTogether property set to Yes and all the controls in that section will not fit on the current printed page. In this case, Microsoft Access prints none of the controls on the current page. Instead, it begins printing the controls at the top of the next page. If it turns out that the section requires more than a single page, Microsoft Access ignores the KeepTogether property value and continues printing the controls at the top of the next page.

The KeepTogether property affects the controls in a form or report section for a single record -- not groups of records. The KeepTogether property will not keep all the grouped records together, and it will not avoid the problem of abandoned group headers left on the bottom of a printed page.

There is a RepeatSection property that is useful for specifying whether a group header is repeated on the next page or column when a group spans more than one page or when a column is desired. The default setting is No so that the group header isn't repeated.

