Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Infinite printing

edited January 2007 in General
I get infinite printing when I got the default prrinter is the Tmt88ii
(thermal POS Printer) and the report is sent to a lexmark inkjet printer.
Also if the default is the lexmark and the report is sent to the thermal
printer I also get infinite printing. If on the program I ask prior to
ppreport1.print command I set the printer to the correct one I don't get the
infinite printing. Where do you suggest I must 'change' the default printer
prior the report is generated. I'm looking for a code that can be put in
every printing command as my standard way of printing.
Is there a way the printig dialog can be force prior to the report been
generated?
Carlos

Comments

  • edited January 2007
    Hi Carlos,

    Are you able to recreate this issue when just printing to the printer (i.e.
    without viewing the report first on screen)? Which version of ReportBuilder
    are you currently using. When printing to a different printer, you need to
    be sure all report components and bands fall within the printer's boundaries
    and that the bands are not larger than a single page. The following article
    may be of some help.

    ------------------------------------------------------
    Article: TroubleShooting: Report Prints Endless Pages
    ------------------------------------------------------

    Occasionally, we have customers state that their reports are in some
    infinite state where page after empty page prints forever.

    There are a few items to check when this occurs.

    The TppReport.AutoStop property is the first thing to check. If this is
    false when the DataPipeline property is unassigned, the endless report will
    be the result. AutoStop is automatically set to True when DataPipeline is
    set to nil, but it is possible to set it back to False. Check for instances
    in your code where you might have created this condition.

    Another thing to check is that all subreports in your report have their
    DataPipeline set. When a subreport does not have its pipeline set, you will
    sometimes see a condition where the first detail record prints and then you
    get blank pages.

    Another, non-data related cause can sometimes be your margin settings. If
    you have stretching bands that need to overflow to the next page, if your
    margins are too tight, sometimes the report engine will endlessly overflow
    to the next page trying to fit the overflow material.

    Still another cause might be having a statically positioned control, set to
    ReprintOnOverFlow, in the same band with a stretching control. For instance,
    if you have a memo set to stretch and in that same band, a label control set
    to ReprintOnOverFlow, then on every page after the first, the memo will
    begin to print after the label control. If the label is placed low enough
    that the memo has no room to print, the report will forever be trying to
    print the overflowing memo on the next page.


    --
    Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited January 2007
    RB pro 10

  • edited January 2007
    Hi Carlos,

    As a test I downloaded the Epson TM-T88II driver, installed it on my machine
    and set it to my default printer. After previewing a simple report I was
    also able to successfully print to my HP LaserJet without any issues. Does
    this behavior occur with every report you print to these printers? If you
    try printing some of the report demos to each printer, do you still get the
    same behavior? Have you tried printing to a different printer other than
    the two you mention?

    --
    Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
This discussion has been closed.