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

Line component on detail doesn't carry to next page when detail splits

edited January 2006 in End User
I am using Delphi 7.01 and RB 7.04.

I have an end user report that has a couple groups on data fields. I want
to use the Line component to show a solid line down the left side on both
group header bands and the detail band. This shows a nice line on the left
that looks continuous. All band heights are dynamic based on the data.

The problem I have is that "sometimes" the line is missed when the entire
band doesn't fit on the page. It only misses it for the first detail band.

I tracked it down to the detail band being cut in half and not having the
option to keep the detail band together. So when the detail band gets split,
it doesn't carry the Line component forward to the second page. This happens
even when the line component is set to parentheight and reprintonoverflow
and stretchwithparent.

I solved it by creating a third group that's grouped on the primary key of
my main query and telling the group to keep together.

Is this a bug?

Any comments or suggestions would be great.

Thanks.

Comments

  • edited January 2006
    Hi Isaac,

    In my testing with the ReprintOnOverflow property set to True, a line will
    re-print when the detail band breaks to a new page. I'm using RB 9.03
    Delphi 7. One other option would be to place a line the size of the page
    inside the PageStyle band. This will print the line behind all the bands of
    the report without interference.

    --
    Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited January 2006
    I won't be upgrade for a while still, but it's good to know that it is
    fixed. I thought about using the PageStyle band, but the pages are dynamic
    meaning that it may not fill the entire page and I wanted the line to stop
    once the report ended. My workaround works for now.

    Thanks for the info.

This discussion has been closed.