Footer.PrintOnLastPage
Hi,
is it possible to print the footerband only on the last page, even if there
is only one ?
Setting PrintOnLastPage only works ig Pagecount > 1. (Because
PrintOnFirstPage is false...
setting it to true makes it go wrong if pagecount>1)
I tried many things, like checking the pagecount in the
"OnEndFirstPass"-event, but that raises an A.V.
Also Footerband.BeforePrint does not work, because if pagecount=1 ., it is
simply not printed...
regards,
Dirk Janssens.
is it possible to print the footerband only on the last page, even if there
is only one ?
Setting PrintOnLastPage only works ig Pagecount > 1. (Because
PrintOnFirstPage is false...
setting it to true makes it go wrong if pagecount>1)
I tried many things, like checking the pagecount in the
"OnEndFirstPass"-event, but that raises an A.V.
Also Footerband.BeforePrint does not work, because if pagecount=1 ., it is
simply not printed...
regards,
Dirk Janssens.
This discussion has been closed.
Comments
I made this with regions and then the foot height dynamic
Within the Code I fill then the Footerband Region with objects and set to
visible depending of my rules for printing them.
Greeting from Turkey (on holiday)
Erich Rieder
Zurich - Switzerland
Thanks for your reply,
My problem is, that I don't how many pages the report will be (stretching
memo's in the detailband).
So where can I determine the pagecount, and still be able to set the
visible-propery ?
Another problem is, that setting the region.visible to false, the band still
occupies the space, right ?
I would like to contunue the detail to the bottom, and print the footer on
the last page...
Finally, the solution must also work for the situation when PageCount=1
*without* the footer, and adding the footer makes the pagecount 2....I
wonder if that it is possible at all !
(In another report, I made a copy with the only difference being the
PrintOnFirstPage-property, and detrmined the recordcount to decide which one
must be printed. Since in this one there are stretching fields, that is not
an option...)
any ideas ?
kind regards,
Dirk.
is
I have to say that this is something that has always bugged me!
Logically, if you tick the checkbox that says "Print on last page",
then the footer should print on the last page **regardless of the number of
pages**
At the very least, the wording on these checkboxes is erroneous:
A tick by "Print on first page" should mean that - but what actually happens
is
that no tick means don't print, which is not quite the same thing.
Roj
I'm glad I'm not the only one ! Since this is such a basic thing, I assumed
I overlooked some property or so.
My guess is (if indeed we havn't overlooked something simple), that this
bugs a whole lot of users.
I'm wondering what there work-arounds are, but wouldn't it be better if this
"bug" would be fixed in the next release (hint,hint) ;(
kind regards,
Dirk.
report to get the absolute page count so that a multiple report can generate
correctly, even when a single page report would print as desired in our
current implementation.
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com
generate
But where do I go from here ??
Do you have *any* idea if what I want it is possible? (I tried a lot)
regards,
Dirk.
Try this:
Set the Report to Two pass
In the FooterBeforePrint section type
Footer.Visible:= (Report.AbsolutePageCount=Report.AbsolutePageNo)
Hope this helps
Roj
Thanks for your help. I think I have little choice here and use your
suggestion, although it's not exactly what I want: setting visible to false
does not make the space available for the detail-band to print all the way
to the bottom.
I really think this is a shortcomming of RB and hope they will find a way to
implement the described behaviour
(that is, "printOnLastPageEvenIfItIsTheFirst" ,
regards,
Dirk Janssens.
about here is a page footer. Report Builder is lacking a report footer.
The report summary works great for this except that it does not print in the
footer position. I realize this can be altered in code, however, this seems
like a basic feature that should be handled at design time.
As for requiring a two-pass report, what are the drawbacks to that? Slower?
I've never even tried one. To over-simplify: why can't the engine determine
that it is done generating pages, back up to the last page and insert the
footer?
could change the engine design to better support the PrintOnFirstPage and
PrintOnLastPage properties and it is on the todo list, however, there are
significant enhancements which are above it on the list. Thanks for the
feedback
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com