Problem: Installed trial version of Amyuni PDF Converter, Evaluation Version Pro 2.10i-3, selected it in VB application as the output printer, wanting the output to go to a pdf file instead going directly to the printer. Pdf file is created but each page size generated if only .04 X .04 and when viewed using the PDFCreativeDoc.exe it shows only Amyuni’s standard Trial version message diagonally across the page. Printer files require a Post Script Level 2 driver and I made sure that the printer option was set that Enabled PostScript Simulation. I did not place any new code in my VB application and since it does know to create the pdf file it would not seem that I needed any.
A document in MS Word is able to successfully create the PDF file when the Amyuni PDF Converter is selected as the printer.
Additional information is that we create a custom page size based on user defined specifications in a text file. In this user-defined file, placement of all items to be printed is defined. Then Printer.Line statements are used to build each item on the page and then Printer.NewPage and Printer.EndDoc eventually prints the pages of the report. Now sure if this is weird and needs special handling.
So questions are:
Should I need any additional code in order to create correct pdf file?
When application is sending output directly to the printer, should it be able to be diverted and sent into a PDF file – even PostScript code?
What corrective steps can I take?
Trial Version - pdf from VB app has empty pages/tiny-0 data!
-
- Posts: 2
- Joined: Thu Apr 15 2004
Hello Lorraine,
Postscript simulation was made only to be used when printing documents with word arts under windows 9x.
To create correct pdf files you need to print your documents to the PDF Printer without checking the 'Print to file' option.
I am not sure if you want to print postscript files to pdf or you want to generate postscript files.
Please send your request to support@amyuni.com so we can check precisely what you are trying to do and we will get back to your with a more accurate reply.
Thanks.
Postscript simulation was made only to be used when printing documents with word arts under windows 9x.
To create correct pdf files you need to print your documents to the PDF Printer without checking the 'Print to file' option.
I am not sure if you want to print postscript files to pdf or you want to generate postscript files.
Please send your request to support@amyuni.com so we can check precisely what you are trying to do and we will get back to your with a more accurate reply.
Thanks.
-
- Posts: 2
- Joined: Thu Apr 15 2004
Re: Trial Version - pdf from VB app has empty pages/tiny-0 d
I figured out the problem. My code was setting custom page sizes and the Amyuni PDF Converter was expecting custom sizes to be entered in twips even though the code set the ScaleMode = 5 which indicated inches.Lorraine Chrisenberry wrote:Problem: Installed trial version of Amyuni PDF Converter, Evaluation Version Pro 2.10i-3, selected it in VB application as the output printer, wanting the output to go to a pdf file instead going directly to the printer. Pdf file is created but each page size generated if only .04 X .04 and when viewed using the PDFCreativeDoc.exe it shows only Amyuni’s standard Trial version message diagonally across the page. Printer files require a Post Script Level 2 driver and I made sure that the printer option was set that Enabled PostScript Simulation. I did not place any new code in my VB application and since it does know to create the pdf file it would not seem that I needed any.
A document in MS Word is able to successfully create the PDF file when the Amyuni PDF Converter is selected as the printer.
Additional information is that we create a custom page size based on user defined specifications in a text file. In this user-defined file, placement of all items to be printed is defined. Then Printer.Line statements are used to build each item on the page and then Printer.NewPage and Printer.EndDoc eventually prints the pages of the report. Now sure if this is weird and needs special handling.
So questions are:
Should I need any additional code in order to create correct pdf file?
When application is sending output directly to the printer, should it be able to be diverted and sent into a PDF file – even PostScript code?
What corrective steps can I take?
Lorraine