doPDF problem printing from Excel
doPDF problem printing from Excel
doPDF problem printing from Excel
Using recent versions of doPDF, I'm experiencing a problem when printing a single page worksheet from Excel.
The page appears to be fine in print preview, but when printed using doPDF the resulting PDF file has the right hand column missing.
When printed using Microsoft Print to PDF the resulting PDF file is perfect; that is, it appears exactly as it did in print preview.
I've uninstalled my old version of doPDF (11.9.347), and installed the latest version (11.9.462) just downloaded from the web site; which by the way, when installed shows 11.9.461 as the version.
Can anyone suggest what the problem might be, and how it can be corrected?
Using recent versions of doPDF, I'm experiencing a problem when printing a single page worksheet from Excel.
The page appears to be fine in print preview, but when printed using doPDF the resulting PDF file has the right hand column missing.
When printed using Microsoft Print to PDF the resulting PDF file is perfect; that is, it appears exactly as it did in print preview.
I've uninstalled my old version of doPDF (11.9.347), and installed the latest version (11.9.462) just downloaded from the web site; which by the way, when installed shows 11.9.461 as the version.
Can anyone suggest what the problem might be, and how it can be corrected?
-
- Posts: 1564
- Joined: Thu May 23, 2013 7:19 am
Re: doPDF problem printing from Excel
Hi, due to a recent Windows update there were problems saving from Excel. We've fixed that in build 465 (released yesterday) so please install the new build. Thank you for reporting this.
Follow us to stay updated:
- Newsletter (get a discount for subscribing): https://www.dopdf.com/newsletter.html
- Facebook: https://www.facebook.com/dopdf
- Twitter: https://twitter.com/dopdf
- Linkedin: https://www.linkedin.com/showcase/dopdf
Re: doPDF problem printing from Excel
Hi Claudiu,
Thanks for the new build - I can confirm that it has rectified the problem.
Thanks for the new build - I can confirm that it has rectified the problem.