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

Problems with Printer Errors

rbuserrbuser
edited July 2001 in General
Dear All,

I wonder whether any of you have a hard time explaining to the
customer why your program (with RB as the report engine) can not print
while product like Excel, Outlook etc. works perfectly OK with the same
printer setup and in the end you have to advice customer to upgrade
their printer driver to a old or a new one to get it to work! Does
anyone have a good explaining for that ?

Any feedback is appreciated.

michael

Comments

  • digitalmetaphorsdigitalmetaphors
    edited July 2001
    When printer drivers are written, they may or may not support all of the
    possible Win API calls that can be made to the printer. Thus, if Excel,
    Outlook or other Windows app can print, it is because the installed printer
    driver supports the API calls that they need in order to print. By
    suggesting updating the printer driver it is hoped that the newer driver
    includes better support for the possible API calls that can be made by
    applications, other the API calls which are needed for Excel, Word,
    Outlook...


    Cheers,

    Jim Bennett
    Digital Metaphors


    Digital Metaphors Corporation
    http://www.digital-metaphors.com
    info@digital-metaphors.com
  • rbuserrbuser
    edited July 2001
    <!doctype html public "-//w3c//dtd html 4.0 transitional//en">

    Dear Jim,

          Thanks for the explaination. If this
    is the case, then is it possible to restrict RB to use a fix set of 'WINAPI'
    call that is known to work in most of the case.

    Thanks

    michael

  • rbuserrbuser
    edited July 2001
    Hi Michael,

    what does one know about printer drivers written in the future?
    You should write a letter to the printer's manufacturer, not to DM.

    regards,
    Chris Ueberall;

    to
    of the case.
This discussion has been closed.