Trouble with Keep Together
Hi Jim, i have tried it and i have the same problem. I'm going to try
explain myself in depth.
Report with a detail band that prints records of a dataset, that is the
datapipeline of the report, that has a lot of fields. Some fields must or
not be printed depending of some values of each record, and when the data is
printed must be contiguous.
I have de detail band with 2 subreports and sr1 has some subreports all with
the property of height dinamically.
---------------------------- Detail Band
sr1
--------------------------------------------------
sr1.1
sr1.2
sr1.3
sr1.4
-------------------------------------------------
sr2
-----------------------------End detail band
Depending of each record, sr1 is printed or sr2 is printed. sr1 has no
datapipeline asigned, and sr2 has a datapipeline that is a list of values
related with each record. sr1.1-sr1.4 does not have datapipelines asigned. i
use this system, because some times sr1.2 and sr1.3 are not printed and i
want that sr1.1 and sr1.4 to be printed together.
sr1 has the property keeptogether activated, and i put the visible and
not visible values of srx.x with RAP int the beforegenerate event of sr1.
The problem is that when sr1 is printed at the end of page, sr1.1 is printed
in one page and sr1.4 (for example) is printed in the next page, and the
property keeptogether of sr1 don't runs.
--
Jes?s Angel Garc?a Zarco
Cointec
explain myself in depth.
Report with a detail band that prints records of a dataset, that is the
datapipeline of the report, that has a lot of fields. Some fields must or
not be printed depending of some values of each record, and when the data is
printed must be contiguous.
I have de detail band with 2 subreports and sr1 has some subreports all with
the property of height dinamically.
---------------------------- Detail Band
sr1
--------------------------------------------------
sr1.1
sr1.2
sr1.3
sr1.4
-------------------------------------------------
sr2
-----------------------------End detail band
Depending of each record, sr1 is printed or sr2 is printed. sr1 has no
datapipeline asigned, and sr2 has a datapipeline that is a list of values
related with each record. sr1.1-sr1.4 does not have datapipelines asigned. i
use this system, because some times sr1.2 and sr1.3 are not printed and i
want that sr1.1 and sr1.4 to be printed together.
sr1 has the property keeptogether activated, and i put the visible and
not visible values of srx.x with RAP int the beforegenerate event of sr1.
The problem is that when sr1 is printed at the end of page, sr1.1 is printed
in one page and sr1.4 (for example) is printed in the next page, and the
property keeptogether of sr1 don't runs.
--
Jes?s Angel Garc?a Zarco
Cointec
This discussion has been closed.
Comments
describe. My subreports are always visible and have datapipelines. Can you
try to set your report up to print correctly, by hardcoding the visibility
and datapipeline assignments? Usually, I try to pare down a problematic
report as much as possible- ie. reduce the dynamic aspects of the report.
In my efforts, the main subreport is keeping together as expected. Perhaps
the best way for me to reproduce your problem is if you could send me a
working example report template that shows this behavior? Send it
support@digital-metaphors.com . I'm interested in seeing the exact timing of
your report and how KeepTogether is being affected.
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com