Home General

11X17 Print Not Working

edited September 2011 in General
When I print an 11x17 (tabloid size) report from the preview screen or
directly to the printer (HP110 Officejet Multifunction) I get a single
smudged line at the top of the paper as though the entire report is at the
top and didn't space properly. (tough to tell tho)

When I save the same report as a PDF first then printing the PDF it prints
OK.

Any ideas of what I might be missing?

Thanks - Jon Gray RB 12.04 Server / Delphi 2007 / Oracle 10G

Comments

  • edited September 2011
    Hi Jon,

    What are you margins set to? Every printer has a non-printable area so
    if the margins fall within this area, items may not print correctly.
    You might try moving the top margin down a bit and see if that solves
    the problem. I believe Adobe Reader scales the page automatically
    before printing.

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited September 2011
    Thanks Nico -

    The margins were at the default of 0.25. I tried several different
    combinations all the way up to 1" margins all the way around and still a
    single 'smudged' line at the top of the page. The line size maybe changed a
    little when the margins were set to 1".

    We installed the latest printer driver too with no change.

    Anything else I can try to resolve it?

    Thanks.
  • edited September 2011
    Several other users are able to print to different printers OK. I suspect
    it's something specific with this one printer that may not be worth chasing.

    In a related issue, the users that can print OK tabloid get 'stuck' on the
    tabloid paper setting even when going back to print a portrait letter size
    report. I see the report is defined using a 'Custom' size instead of a
    predefined paper option. Is this what's making the tabloid / custom setting
    stick? Previously the paper was properly selected based on the report
    definition letter protrait or landscape legal.


  • edited September 2011
    This issue has been resolved, it was our problem not reportbuilder.
This discussion has been closed.