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

odd printer behaviour

edited November 2008 in General
Dear all,
I wonder if anyone has experienced this.

At a customer site, they are using a thermal printer to print labels for
plants and trees.
I am using the report designer tool and using loadfromtemplate to create
labels as required. In the code it sets the printer name. So far so good.
A sales order is processed and a print job created for each line (they may
use different label templates per line).
The print jobs appear in the print queue, however the odd print job assigns
itself to COM1 instead of LPT1

This then either fails to print, or halts the whole process.

Is there anything I can set that forces it to use LPT1, has anyone ever seen
this before?

I appreciate it may have nothing to do with Reportbuilder but I thought I
would ask.

regards

John Evans

Comments

  • edited November 2008
    Hi John,

    We have not seen anything like this before. Does it only happen when
    printing reports to this specific printer? If you for instance export the
    report to PDF then print from Adobe, does the report print to the correct
    port? ReportBuilder doesn't directly interact with the printer driver. It
    calls generic Windows API commands which in turn communicate with the
    printer.

    Check to be sure you are using the latest printer driver for the printer you
    are having problems with.

    --
    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.