MSAcess 2003 Report Page Break Problems

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Dave

    #1

    MSAcess 2003 Report Page Break Problems

    I have a report set up with the following hierarchy in the design mode
    _______________ ___________
    PAGE HEADER
    PRODUCT HEADER
    PRODUCTDESCRIPT ION HEADER
    DETAIL
    PAGE FOOTER
    _______________ ___________

    The problem is that when my report is generated the PRODUCT HEADER and
    the PRODUCTDESCRIPT ION HEADER will show up on the page which is great,
    but sometimes it will be at the bottom of a page and the DETAILS will
    come out on the next page without these headers. Is their a way I can
    put some code in so that if ALL of the DETAILS section underneath the
    headers does not fit on the current page then a page break will occur
    and the headers and the DETAILS section will be listed in it's
    entirety on the next page. Any help would be greatly appreciated.
    Thanks
  • Brian

    #2
    Re: MSAcess 2003 Report Page Break Problems

    "Dave" <haleswd@yahoo. com> wrote in message
    news:e8499a21.0 410051202.2731d 67b@posting.goo gle.com...[color=blue]
    > I have a report set up with the following hierarchy in the design mode
    > _______________ ___________
    > PAGE HEADER
    > PRODUCT HEADER
    > PRODUCTDESCRIPT ION HEADER
    > DETAIL
    > PAGE FOOTER
    > _______________ ___________
    >
    > The problem is that when my report is generated the PRODUCT HEADER and
    > the PRODUCTDESCRIPT ION HEADER will show up on the page which is great,
    > but sometimes it will be at the bottom of a page and the DETAILS will
    > come out on the next page without these headers. Is their a way I can
    > put some code in so that if ALL of the DETAILS section underneath the
    > headers does not fit on the current page then a page break will occur
    > and the headers and the DETAILS section will be listed in it's
    > entirety on the next page. Any help would be greatly appreciated.
    > Thanks[/color]

    I may be missing something here, but don't you simply need to experiment
    with the KeepTogether property, and maybe the ForceNewPage property, for the
    groups in question?


    Comment

    Working...