Pagination Problem (reverse of page duplex)
Hi
I am printing terms & conditions on the reverse of invoices using the
techniques explined in Tech Tips, Pagination, Duplexing: Printing a
Disclaimer on the Back of Every Page. I have been using this technique for
some time and whilst I dont think it is the most elegant solution it does
work. I have however hit a problem.
The report is made up of two data pipelines; the invoice header (1 record)
and the invoice items (multiple). The invoice items are free text items
with a dbMemo field (for the description) and a dbText (for the amount).
Usually the description is no more than a few lines and there is no problem
handling lots of items running to multiple pages. If however the
description for one item runs to more than a page full on its own then the
report will not generate correctly. It just runs away with page numbers
going off the clock. If there are no terms & conditions (ie a simple non
duplexed invoice) then there is no problem.
Does any one have any ideas on how to resolve this or is the only solution
to make sure that the description does not exceed a certain length.
Regards
Tim Murfitt
I am printing terms & conditions on the reverse of invoices using the
techniques explined in Tech Tips, Pagination, Duplexing: Printing a
Disclaimer on the Back of Every Page. I have been using this technique for
some time and whilst I dont think it is the most elegant solution it does
work. I have however hit a problem.
The report is made up of two data pipelines; the invoice header (1 record)
and the invoice items (multiple). The invoice items are free text items
with a dbMemo field (for the description) and a dbText (for the amount).
Usually the description is no more than a few lines and there is no problem
handling lots of items running to multiple pages. If however the
description for one item runs to more than a page full on its own then the
report will not generate correctly. It just runs away with page numbers
going off the clock. If there are no terms & conditions (ie a simple non
duplexed invoice) then there is no problem.
Does any one have any ideas on how to resolve this or is the only solution
to make sure that the description does not exceed a certain length.
Regards
Tim Murfitt
This discussion has been closed.
Comments
When using the technique in the Tech-tip article, you are correct in that
you are restricted to single page groups. If you need to overflow to
separate pages, you will need to take a different approach similar to the
SpreadSheetStyle example of printing pages to memory, then reordering them
before they are sent to the printer.
http://www.digital-metaphors.com/tips/PrintLegaleseOnEvenPages.zip
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Thanks for the response. I have had a quick look at the zip file you sent
and run the application. I need to take a bit more time to work out how it
all works and how I can adapt it to what I do but it looks very
interresting. Usually the terms & conditions i have to print are in a rtf
file which i usually load from file into a RichText component. Presumably
that would work in a similar way. Also my report is usually saved and
loaded from a rtm file. Again I assume that would be no problem.
Regards
Tim