Thermal Printers

rbuser

We have report builder, and we would like to start using it with our
high speed thermal printers. The problem that we are having is that
when we use report builder the printers print slower. I know this has
to do more with the driver. What we have been doing is using PCL to
print directly to the printers, but now our users want more design
capabilities. I would like to give them this using Reportbuilder, but I
know they will not be happy with the speed. Is there someway that I can
use Reportbuilder and get the speed I want.

Paul Loucks

nicocizik

Hi Paul,

There are many factors that could slow down printing when using
ReportBuilder. First, data access, once you print a report, it has to
access your database and retrieve any data that needs to be displayed on
your report. This is usually the main cause of slow printing. Also if you
are printing multiple copies of a report, you can let the printer handle
this instead of RB by setting the Report.PrinterSetup.DelegateCopies to
True. ReportBuilder uses the same Windows API calls to talk to every
printer driver so as you mentioned below, it could be how this driver
handles these specific commands that is slowing things down as well.

--

rbuser

In order for you to get the benifits of a Thermal Printer you have to go to
PCL. I was just wondering if there was a way for Report builder to get around
the API. Thermal Printers are faster than standard ink jet or laser. Have you
ever tried a line printer using windows, it really defeats the purpose of
having a line printer. Windows API is just not fast enough for it.

How about this is there away to catch the PCL code after the API is done with
it, and then send that to the printer. It will take longer sending it but you
will make up for it with the speed of the printer.

Paul

nicocizik

Hi Paul,

Once your printer driver has created the PCL code, ReportBuilder no longer
has any control of it. You would probably need to write some external
Delphi code that extracts the PCL code at this time. I am however unsure
this will speed any thing up. ReportBuilder must use the Windows API to
render to the printer device. If the API is what is slowing you down, I do
not see how catching the PCL code afterward will speed things up any.

--