PDF Converter Version 2.1 developer version.
When a user chooses acrobat printer driver as the printer to use, and then later chooses the function in my application that uses the amyuni converter to generate a file, the acrobat printer driver is actually used and not the amyuni converter! It is as though the acrobat printer driver doesn't let go of being the default printer.
PB 7
Any suggestions?
Mike
Acrobat printer driver interferes
Hello,
As far as I know, Powerbuilder 7 prints to the default printer of the system while Powerbuilder 8 prints to the specific printer of the application.
So if you have Powerbuilder 7, you need to set the PDF Converter as default before printing to it, unless you have a way to set it as the default printer of your datawindow.
In Powerbuilder 8 things are easier, you can call:
dw_1.Modify ('DataWindow.Printer="My PDF Printer" ')
to set the printer of your datawind to the PDF printer, in this way your datawindow will be always printed to the PDF Printer.
Hope this helps.
As far as I know, Powerbuilder 7 prints to the default printer of the system while Powerbuilder 8 prints to the specific printer of the application.
So if you have Powerbuilder 7, you need to set the PDF Converter as default before printing to it, unless you have a way to set it as the default printer of your datawindow.
In Powerbuilder 8 things are easier, you can call:
dw_1.Modify ('DataWindow.Printer="My PDF Printer" ')
to set the printer of your datawind to the PDF printer, in this way your datawindow will be always printed to the PDF Printer.
Hope this helps.
Perhaps I should have mentioned that this is the developer version I am working with. I am using the dll interface.
As you know, the dll interface does that automatically already for PB 7.
It works fine when the default printer is set to a regular printer. It also works fine when a user selects a new 'regular' printer in the application.
It doesn't work when the adobe acrobat printer driver is selected. It is as though the PDF converter dll sees the adobe printer driver as the same as the amyuni pdf printer driver and it does NOT change it.
As you know, the dll interface does that automatically already for PB 7.
It works fine when the default printer is set to a regular printer. It also works fine when a user selects a new 'regular' printer in the application.
It doesn't work when the adobe acrobat printer driver is selected. It is as though the PDF converter dll sees the adobe printer driver as the same as the amyuni pdf printer driver and it does NOT change it.
Hello,
Please check the declaration of SetFileNameOptions(), this functions takes two long paramters, if you are passing to it a long and an integer than this could be the source of your problem.
If this is not the case, please send your functions declarations to support@amyuni.com so we can check them and see if there is any problem with those declarations.
Best Regards.
Please check the declaration of SetFileNameOptions(), this functions takes two long paramters, if you are passing to it a long and an integer than this could be the source of your problem.
If this is not the case, please send your functions declarations to support@amyuni.com so we can check them and see if there is any problem with those declarations.
Best Regards.
Last edited by Joan on Thu Jun 10 2004, edited 1 time in total.
Hello,
The new version of SetFileNameOptions takes a large number of values, some of them are integers (Example NoPrompt, UseFileName, ect...) and some are Longs (Example: ExportToRTF, PostProcessing, ect...).
If you need to use Long values you need to declare SetFileNameOptions as taking two Long.
I am sure our Technical Wirter will include this issue when updating the documentation of the Developer version of the driver.
If you are still facing problems please send your declarations and a snippet of your code to support@amyuni.com so we can check it.
Thanks.
The new version of SetFileNameOptions takes a large number of values, some of them are integers (Example NoPrompt, UseFileName, ect...) and some are Longs (Example: ExportToRTF, PostProcessing, ect...).
If you need to use Long values you need to declare SetFileNameOptions as taking two Long.
I am sure our Technical Wirter will include this issue when updating the documentation of the Developer version of the driver.
If you are still facing problems please send your declarations and a snippet of your code to support@amyuni.com so we can check it.
Thanks.