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

Screen Printer does not support printing

edited February 2008 in General
Using D6 w/RB9.03

A user is getting the EPrintError Screen Printer does not support printing.
They get this a couple times a day even after successfully printing the same
report several times. Closing my application and opening it again always
solves the problem. It appears to me like RB is loosing the connection to
the Windows Printer.

Any ideas?

Thanks,
Perry

Comments

  • edited February 2008

    - Could be caused by the app leaking resource. Try using a tool such as
    FastMM or AQTime that can check for leaks.

    - If the app is running under something like Citrix, then might be that it
    is losing connection to a windows printer.

    - if the printers are being installed/uninstalled while the app is running,
    then that could cause an issue as well.


    --
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited February 2008
    Is this also the cause of a 'Canvas Does Not Allow Drawing' error?

  • edited February 2008

    Yes. That error indicates the application cannot get a handle to a valid
    device context. For screen preview, the screen device context is used and
    for print, the printer device context. If the app can preview and print at
    start up and then later throws 'Canvas does does not allow drawing' errors,
    then the application is most likely leaking memory/resources. If the app can
    preview by not print - then perhaps there are no valid printers available.



    --
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited January 2009
    If the connection to the printer is interupted because of a network issue,
    do you know of any way to reestablish the connection from within the Delphi
    app?

This discussion has been closed.