I have such problem, if report is printed to .pdf directly it creates file difrrent than if I use option Export to PDF from preview menu.
Its same report just printer 2 times with out without preview mode.
With preview mode it create file in my example with size: (1,503,600 bytes test-a.pdf) and as far I can see is %PDF-1.3 version
but if I use preview mode and export it create five with size: (203,198bytes test-b.pdf) and its %PDF-1.5 version ?!
TPrinter problem
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
Re: TPrinter problem
Do they have the same content even if they are using different versions ?
- nageswaragunupudi
- Posts: 8017
- Joined: Sun Nov 19, 2006 5:22 am
- Location: India
- Contact:
Re: TPrinter problem
When we export to PDF from Preview, the preview class first checks if MSWord is installed. If installed, the document is first exported to Word and then saved as PDF. This produces PDF with high quality and very small size.
In case Word is not installed, then the preview class uses the FWH built-in function FWSavePreviewToPDF(). This function does the job but is not efficient like MS Word and produces a file with large size.
When we directly export from Printer/Report, directly the inbuilt function FWSavePreviewToPDF() is used, producing a file larger than what Word would have produced.
This explains the reason for the different sizes and versions.
This also raises a question why can not exporting to PDF directly from Printer/Report can also adopt the same approach. Answer is yes. But this takes some time and we shall try to provide this in future versions.
In case Word is not installed, then the preview class uses the FWH built-in function FWSavePreviewToPDF(). This function does the job but is not efficient like MS Word and produces a file with large size.
When we directly export from Printer/Report, directly the inbuilt function FWSavePreviewToPDF() is used, producing a file larger than what Word would have produced.
This explains the reason for the different sizes and versions.
This also raises a question why can not exporting to PDF directly from Printer/Report can also adopt the same approach. Answer is yes. But this takes some time and we shall try to provide this in future versions.
Regards
G. N. Rao.
Hyderabad, India
G. N. Rao.
Hyderabad, India
Re: TPrinter problem
I use free eDocPrintPro Printer-Driver to make PDFs and other formats.
http://www.pdfprinter.at/en/
http://www.pdfprinter.at/en/
- nageswaragunupudi
- Posts: 8017
- Joined: Sun Nov 19, 2006 5:22 am
- Location: India
- Contact:
Re: TPrinter problem
Doesn't this require installation on all client PCs ?byte-one wrote:I use free eDocPrintPro Printer-Driver to make PDFs and other formats.
http://www.pdfprinter.at/en/
Or are you using SDK/DLL integrated into your application?
Regards
G. N. Rao.
Hyderabad, India
G. N. Rao.
Hyderabad, India
Re: TPrinter problem
For now i use installation on all clients. But every Printer-Driver lets install on the LAN for access from all clients!?
Re: TPrinter problem
Hi Günther,byte-one wrote:I use free eDocPrintPro Printer-Driver to make PDFs and other formats.
http://www.pdfprinter.at/en/
How to use eDocPrintPRo to print to pdf silently? I mean, how do we programmatically assign the filename and output path?
TIA
FWH 11.08/FWH 19.03
xHarbour 1.2.1 (Rev 6406) + BCC
Harbour 3.1 (Rev 17062) + BCC
Harbour 3.2.0dev (r1904111533) + BCC
xHarbour 1.2.1 (Rev 6406) + BCC
Harbour 3.1 (Rev 17062) + BCC
Harbour 3.2.0dev (r1904111533) + BCC
Re: TPrinter problem
hua, see on the picture the settings: %DOCNAME% as filename. Also the path can set with %-variables.
http://byte-one.com/edoc.png
http://byte-one.com/edoc.png
Re: TPrinter problem
Thank you Günther
FWH 11.08/FWH 19.03
xHarbour 1.2.1 (Rev 6406) + BCC
Harbour 3.1 (Rev 17062) + BCC
Harbour 3.2.0dev (r1904111533) + BCC
xHarbour 1.2.1 (Rev 6406) + BCC
Harbour 3.1 (Rev 17062) + BCC
Harbour 3.2.0dev (r1904111533) + BCC