the report size is custom size. when print, the right portion is disappear sometimes!! But preview has not this problem, what is the reason and how to fix it? I am using reportBuilder 7.03
Be sure that your margins are set large enough to keep all report components within the printable area allowed by the printer you are using. If report components fall in the un-printable area for a device, they will in most cases not be printed. Most printers require at least a 1/4 inch margin.
This is not a known issue. Are you able to print to other printers? Does the same printer work with other paper sizes? Be sure you are using the latest version of the driver for the printer you are using and that it supports custom paper sizes.
I have seen a maybe related issue before. When printing our reports the memo and RTF memo fields were cut off so that only the left half of the page was printed at. It only affected memo's though. We figured out that it was related to the proint driver in that case. Maybe that helps.
Comments
Be sure that your margins are set large enough to keep all report components
within the printable area allowed by the printer you are using. If report
components fall in the un-printable area for a device, they will in most
cases not be printed. Most printers require at least a 1/4 inch margin.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
This is not a known issue. Are you able to print to other printers? Does
the same printer work with other paper sizes? Be sure you are using the
latest version of the driver for the printer you are using and that it
supports custom paper sizes.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
I have seen a maybe related issue before.
When printing our reports the memo and RTF memo fields were cut off so that
only the left half of the page was printed at.
It only affected memo's though.
We figured out that it was related to the proint driver in that case.
Maybe that helps.
Stephan