Subrpt w/ regions - regions reprinting

rbuser

Hey All,

This a continuing problem and was prev. posted under ironboyzz a while back.

Been having a problem where variable length dbrichtext within subrpt/region
reprinting on

next page ... changing the offsets on rgns temp fix per report but unable to
find

why/where/what a setting that will stop dupe on next page for reports. Since
rgns are

vairable as whether they print or not, had played with shiftrelto, keep
together etc.. Also

did reass of shiftrelto real-time as per prior post advice here.
It is a very complex report so not so easy to just send example.

Length of text or lack of text within dbrichtext dictates whether or not
printed and how

much space on page to be used(varible).

Runs like this:
Subreport on detail band>
Several Regions>
All set to keep together
All shiftrelto = prior (tried reass when no print of prior ng)
All shiftrel to parent = false
All ReprtonOverflow = false
Stretch = True
Within Each Region>
Caption Label and DBRichtext
All set as keep together
DBRichText >
All Stretch,transparent=true
All ReprtonOverflow = false
All set to keep together


rgn1 prints
rgn2 prints
rgn3 not vis(empty text) - rgn visible/not DOES NOT change reprint of next
rgn
rgn4 prints (current page)
-- page break
rgn4 reprints

nardmoseley

As an alternative to the Regions, you might try using SubReports. If a
subreport is not connected to a datapipeline, it will print a single detail
band and stop. You can still connect the data-aware objects in the subreport
to a datapipeline - they will simply print the data from the current row.

Subreports are better at containing stretchable objects than the region. The
region is much more simplistic.

You definitely need to manage the ShiftRelativeTo relationships so that only
the visible objects are used in the chain.


--
Nard Moseley
Digital Metaphors Corporation
www.digital-metaphors.com

rbuser

Awesome, got the problem fixed. It was definitely the Shiftrelativeto but
checking visibility and setting the SRT in the Band.OnPrint was causing
havoc so moved check to OnOpen of DBPipe and was able to check and set
there. RE: regions vs. subreports ... its working fine with both in levels
(subrpt>rgns) . Only thing that i noticed is that the OnOpen of DBPipe event
fires a few times ..Any thoughts about??>>

Tks for the help!!!

nardmoseley

In its current implementation the DataPipeline.OnOpen event fires each time
DataPipeline.Open method is called. The event is fired regardless of whether
the datapipeline is already active. It does not check whether the
datapipeline is already active.

Likewise, I think the report engine probably calls Open without checking
whether the datapipeline is already open.



--

Nard Moseley
Digital Metaphors Corporation
www.digital-metaphors.com