Subreports & page spans...

rbuser

Hi,

I'm having troubles with a subreport that spans multiple pages. A few things
come to mind:

1) if "Keep together" is True, but the report/section/whatever doesn't
fit entirely on a new page, there's no need to start a new page in the
first place.

2) This particular subreport stops after the first page and doesn't print
on the next page, so it doesn't display all information.

3) Is it possible to repeat headers/titles in subreports that span multiple
pages? (that is, if the data would display in the first place :-)

--

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird & MS SQL Server.
Upscene Productions
http://www.upscene.com

nicocizik

Hi Martijn,

1. With KeepTogether set to True, a subreport by definition will try to
move itself to a new page if there is not enough room on the current page.
I am a bit unclear the problem you are expriencing.

2. Please send a small example of this issue to
support@digital-metaphors.com and I'll take a look at why all your
information is not being printed in your subreport.

3. If you are using Child style subreports, Headers and Footers will not be
displayed. Try placing a group header around the entire subreport based on
a static label and set Print header on subsequent pages to true.

--

rbuser

Hi Nico,


Yes, I know thats the current behaviour :-)

Imagine this, every page takes 5 of these: [ ]

page 1:
[ some header or detail part ]
[ with some more info ]
[ ] ( = empty space )
[ ]
[ ]

page 2:
[ a subreport that didn't fit on page 1 ]
[ more subreport data ]
[ more subreport data ]
[ more subreport data ]
[ more subreport data ]

page 3:
[ more subreport data ]
[ more subreport data ]
[ more subreport data ]
[ next detail row from the main report ]
[ more detail data ]

Why does the subreport start on page 2, as it cannot be completed
on page 2 anyway? There's A LOT of waste space on page 1.


I'll try creating one.

be
on

The Title part seems visible for subreports. I was wondering if it could be
made repeating for subreports that span multiple pages, so, for column-
like data, you know what you're watching...

--
Martijn

nicocizik

Hi Martijn,

1. Where would you like the subreport to begin printing? ReportBuilder is
working as designed. With KeepTogether set to True, the subreport will move
to the next page. If it is then too big to fit on the entire next page, it
has no other choice but to print on the third page. If you take
KeepTogether off, it should fill up the empty space on page 1.

2. I looked at your example and found that you are trying to close your
detail pipeline in the Master's OnRecordPositionChange event. You cannot
close a pipeline while the report is generating or this will not give you
correct results. Also, if you are trying to make a master/detail style
report using JITPipelines, you should use datapipeline linking and let
ReportBuilder take care of the output. For an example of a Master/Detail
report using JITPipelines, please see the ReportBuilder Demos #139.

3. Yes the Title band in a Child Subreport will display but there is no way
to make it repeat itself. As I said before, you will need to create a group
around a static variable and use the group header band as a subsitute.

--

rbuser

Hi Nico,

is
move
it

Well, "Off" it is then.


No, no - remember: we exchanged emails about this some time ago. It's
not a matter of having a long list of detail rows that need to be matched
and filtered for some master row. It's a matter of only knowing the amount
of detail rows per master - that's why I'm using subreports. And it works
great for all reports, except for the issue that they don't print across
pages.

If you can find another way of doing this - share it. But it's NOT a simple
master/detail relationship.

way
group

Care to add a property "Repeat On Additional Pages" to the title of a
subreport?


--

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird & MS SQL Server.
Upscene Productions
http://www.upscene.com

nicocizik

Hi Martijn,

Sorry, I had forgotten about our discussion on using a Master/Detail
relationship with JITPipelines. Still, the reason you are loosing some of
your data is that you are closing your detail pipeline during report
generation. If you can find a way to avoid this, your reports will generate
a lot smoother.

Thanks for the suggestion about the repeating Title Band option.

--

rbuser

Hi Nico,

generate

Hmm - I thought I _had_ to close the pipeline in order to change the
record count.

I'll fiddle a bit more. It seems it I open it directly afterwards - I might
get better results.

Thanks.


--

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird & MS SQL Server.
Upscene Productions
http://www.upscene.com

rbuser

Hi Nico,

is
move
it

You know, I was thinking - what perhaps makes even better reports
is this (all for subreports, of course):

KeepTogether = True
-> but, if it doesn't fit on the next page in one go, also make it display
on the current page, IF at least 1 detail row can be fully printed.

MoveToNextPageIfNoDetailRowCanBePrinted :-)
-> move to the next page if not at least one detail row from the sub-
report can be printed.

This gives much greater flexibility in designing reports with a minimum
of wasted space when printing, right?

--

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird & MS SQL Server.
Upscene Productions
http://www.upscene.com