Home› General
ReportBuilder 22.06 now available including Delphi 12.2 support!
New Blog Posts: Merging Reports - Part 1 and Part 2

Printing Directly to the Printer

rbuserrbuser
edited May 2003 in General
I have a customer that is printing a report directly to the printer
bypassing the preview form and they get to about 2100 pages and get an
out of memory error. In trying to duplicate the problem myself, I
instead of printing to a printer, I printed directly to adobe (not
from extra devices), adobe is setup as my default printer. I was
unable to duplicate the problem and got up to about 2300 pages and it
was still printing. My question is the following: It seems to me
that printing directly to an actual paper printer or printing to adobe
for testing a memory leak will not make a difference to anything in
the report writer. Is this true? The only difference I could think
of is that maybe it is some kind of memory leak in the printer
driver. Can you think of anything else? I did run the report thru a
delphi memory leak program and came up with no leaks.

Comments

  • nicociziknicocizik
    edited May 2003
    Jeff,

    Yes this is true. When ReportBulder prints to a device, the only code which
    will be different will be the device class. Try having your customer update
    the printer driver they are using. You can also try downloading the printer
    driver and installing it on your computer (without an actual printer) and
    printing to the spooler. If you then print using that driver, the pages
    will be spooled but not printed. This way you can test the possibility of a
    memory leak in the driver using Automated QA or Sleuth QA Suite.

    --
    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • rbuserrbuser
    edited May 2003
    Hi1

    Maybe you should install the same printerdriver and change the
    printdestination in the printerdriver to Save To File.

    HTH

    Gruß aus den Bergen
    Günter
  • rbuserrbuser
    edited May 2003
    Hi,
    I had a same problem when testing ReportBuilder on forms on one printer
    driver (original HP driver for LaserJet2100) while on Microsoft WinXP HP
    LaserJet 2100 driver seemed to work fine.
    After spending some paper we finally concluded that there must be some kind
    of bug in Report Builder when labels passed through bottom margin. It
    happened to me, that one report could print page 1 and 2 (although there was
    no page 2) could print forever. The problem was then to increase paper
    length a bit or reduce top margin.
    Also what I discovered was that if You set left margin too small (negative),
    then margin was set back to default of printer, not 0.
    So try to increase length of paper for a 1 cm or so and maybe this would
    solve Your problem.

    Best regards,
    Goran Brumen


    "Jeff Ferris" je napisal v sporocilo
This discussion has been closed.