Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Recurring Page

edited June 2001 in General
Hi, using D5E and RBE (latest version). Have two groups
and the second group has keep group together and reprint
group header on subsequent pages. The first group has
start new page and reprint group header. When the 2d
group header exceeds a page (I did not expect this to
happen but you know how clients are ), I get the same
page over and over. This seems to be a bug but maybe
(once again), I missed something in RB.

Thanks.

Comments

  • edited June 2001
    It's not really a bug. The first group header reprints on every subsequent
    page, and the second group header is always trying to print, but can't there
    isn't enough space for it to print, ever, because the first group header is
    trying to print as well. An exception used to be raised in the designer
    when the page height is exceeded, but this only was applicable to static
    band heights. We could perform a check at runtime. We'll have to think
    about the best way to approach this issue. You can always hit 'Cancel' when
    infinite pages are generated, and return to the design workspace. Granted,
    it would be nice if RB could stop the generation process and tell the user
    the cause of the problem.


    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited June 2001
    I tried splitting the second group into two groups (both grouping on
    a Nmbr field). The 2-first had a single line title and the 2-second had the
    rest of the "verbiage". The 2-first had reprint and the 2-second did not. I
    also used Keep together. I had to discard this approach as the 2-first
    would print the single line title on a page and then jump to the next page
    to reprint it and the 2-second; this occurred even when the "verbiage"
    wasn't long enough to give problems.

    BTW, I would think that it would be nice to have RB override the settings
    when they become "impossible" and continue printing the report. My users
    would certainly say that a "bad-looking" report is much better than no
    report at all.

    Thanks.

  • edited June 2001
    Thankyou, for the suggestions. If the report is to continue generating,
    there should at least be some hint to the user, in which the report couldn't
    generate correctly because of a page height conflict.


    Cheers,

    Jim Bennett
    Digital Metaphors


This discussion has been closed.