cgosbee
Posts: 23
|
Posted: 01/22/2008, 12:45 PM |
|
Is there any reasonable way of ensuring that you avoid "widowing" in reporting?
If I do a report with group levels, such as
TOP LEVEL
MIDDLE LEVEL
BOTTOM LEVEL (detail level, really)
BOTTOM LEVEL
BOTTOM LEVEL (repeats)
MIDDLE LEVEL
BOTTOM LEVEL (detail level, really)
BOTTOM LEVEL (repeats)
TOP LEVEL
etc.
the report will invariably end up with things like having only TOP LEVEL for the next level as the last report line on page 1. Or, it might be TOP, MIDDLE, and all detail pushed to the next page. Or, it could be that some detail is on page 1, the rest on page 2, and so on.
I can see how "fixing" this might be difficult, if it is possible, but in web mode, is there any way to force TOP LEVEL to always start on the next page? This might not be perfect, as line limits for a page could still cause TOP LEVEL's details to flow to new pages, but it would still be a step in the right direction.
|
|
|
DonB
|
Posted: 01/22/2008, 2:36 PM |
|
Define whatever html element that is at the start of a page with the CSS
'page-break-before:always' attribute/value. If you make that an <H1> for
example, define it as <H1 style="page-break-before:always">. Of course,
being a good developer, you would put that in your style sheet, not embed it
into the page markup. Any element that happens to be what you want at the
start of the page can be used, not necessarily the <H1>. the screen will
ignore it, but you will see the page break when printing. Browsers don't
know how 'tall', or even what, a 'page' is, so the styling is meaningless
on-screen.
--
DonB
http://ccswiki.gotodon.net
"cgosbee" <cgosbee@forum.codecharge> wrote in message
news:4479655d0ae889@news.codecharge.com...
> Is there any reasonable way of ensuring that you avoid "widowing" in
> reporting?
>
> If I do a report with group levels, such as
>
> TOP LEVEL
> MIDDLE LEVEL
> BOTTOM LEVEL (detail level, really)
> BOTTOM LEVEL
> BOTTOM LEVEL (repeats)
> MIDDLE LEVEL
> BOTTOM LEVEL (detail level, really)
> BOTTOM LEVEL (repeats)
> TOP LEVEL
> etc.
>
> the report will invariably end up with things like having only TOP LEVEL
> for
> the next level as the last report line on page 1. Or, it might be TOP,
> MIDDLE,
> and all detail pushed to the next page. Or, it could be that some detail
> is on
> page 1, the rest on page 2, and so on.
>
> I can see how "fixing" this might be difficult, if it is possible, but in
> web
> mode, is there any way to force TOP LEVEL to always start on the next
> page? This
> might not be perfect, as line limits for a page could still cause TOP
> LEVEL's
> details to flow to new pages, but it would still be a step in the right
> direction.
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.yessoftware.com/
>
|
|
|
cgosbee
Posts: 23
|
Posted: 01/22/2008, 2:48 PM |
|
Thank you.
I had this (the print separation) working (although, I should probably look into what you are describing with the styles, too), but I was actually more concerned with the paging in web view (with respect to the navigator, and the "automatic" paging that CodeCharge is doing for me).
In other words, if 50 rows on page one causes my TOP LEVEL summary to show as the last line on page 1, and you have to click to page 2 to see the rest, I would like to be able to "force" TOP LEVEL to start on page 2 instead (when viewed on the web, not just for printing purposes). I have a sneaking suspicion this is either not possible, or is at least prohibitively time-consuming to achieve.
|
|
|
|