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

keeping contents of a detail band together

edited December 2013 in General
I have some into a project recently, and am trying to resolve an issue
in a report. I have a TppDetailBand which contains a TppDBWPTRichText,
and two TppRegions. The TppDBWPTRichText may contain zero to n lines of
text.

Is there a way to keep the band from breaking across page boundaries?

Thanks,

Bill Meyer

Comments

  • edited December 2013

    Thanks, Nico, I suspected that would be the path. The existing design,
    however, uses those regions, one for the header row, and the other for
    data rows. The regions can't be nested in the subreport, can they?
    Because if not, then I must change a good deal of code which now
    populates the report.

    Thanks,

    Bill Meyer
  • edited December 2013
    Hi Bill,

    Since ReportBuilder does not support nested regions, you could place all
    your detail components inside a KeepTogether subreport to accomplish
    what you need.

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited December 2013
    Nico,

    In the interest of a minally disruptive rework, I put a subreport in
    the band, and put the original components that had been in the band
    into the subreport.

    Now I observe that the region which previously showed the bold-faced
    headers above the data rows is no longer present, and the subreport
    still breaks across page boundaries.

    It occurs to me that you may be recommending a feature not present in
    the version I must use: 12.04. Could that be?

    Thanks,

    Bill Meyer
  • edited December 2013
    Update. It finally occurred to me to put the RTF and header region into
    the title section of the subreport.

    On the main report, I have selected the subreport, and set
    KeepTogether. However, the subreport -- typically one title roe and
    three data rows, will still break across a page boundary. This is what
    I need to correct.

    Thanks,

    Bill Meyer
This discussion has been closed.