A region within another region not possible?

rbuser

Hello,
it looks as if it's not possible to place a region within another region.
I could really use this functionality, since it's possible to place other
elements within a region AND to let it / them move in relation to X at the
same time.

The usage would be to have one big region, which shall keep it's content
together and stretch. Within it there would be some other regions (among
other elements), which are placed below each other and can be visible or
invisible depending on the data. If some of them are not visible and there
are some remaining visible regions below, those remaining regions shall
"move" up and the big region shall adjust it's size, but still keep
everything together.

With the current functionality it's necessarry to move those visible /
invisble elements manually via RAP.

Is there any reason, why it is not possible to place a region within another
one?

Regards,
Mark

nardmoseley

Regions are simple containers - they are very limited.

The solution is to use Subreports rather than Regions.

SubReports can contain multiple stretching objects, be it Regions or other
Subreports.


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

rbuser

Hello,

if I place a SubReport on the detailband and move single fields I have there
now to that SubReport, in which section of the SubReport should those fields
be placed? I.e. on the Titleband, Detailband another band?

Kind regards,
Mark

nicocizik

Hi Mark,

If you are just using the subreport as a nested container, I suggest
using the detail band with any other bands' visibility property set to
False.

rbuser

Hi Nico,

that's what I would like to use the SubReport for, yes. Just to have better
control about the "KeepTogether" property etc. as was suggested in some
other topics, because regions don't work properly.

Does the DataPipeline of the SubReport has to be set to the same
DataPipeline as in the main report or is that not necessary?

nicocizik

> because regions don't work properly.

I believe the regions are currently working as designed .

You should not need to set the datapipeline of the subreport unless you
wish the subreport to traverse your dataset itself.