Occassionally one of our users gets an error where instead of printing a Word document to the PDF converter it tries to print it to a hardware printer (which seems to cause the printer a lot of problems). This occurs on both administration machines when using PDFDriverInit, and on non-admin machines where we've run install.exe and call DriverInit instead (this is version 2.10 of PDF Converter).
His system is fairly standard (Win XP Pro, Office 2003) although he does have a bit of software called Spindle installed which can output to PDFs, so perhaps there is a conflict there?
As I said, this only happens occassionally, the rest of the time it works fine. I'm not sure if anyone else has encountered a similar error and managed to find a solution?
Thanks
Printing to hardware printer
Hello,
From the above description i can't be sure what is happening on your customer's site, maybe other users who faced a similar issue can give more information.
I can however tell you what could typically cause a similar situation:
1 - If your application is trying to print to the Default printer of the system and the physical printer is set as default instead of the PDF Printer.
2 - If your application prints to a sepcific printer set from inside the application and at a give time the physical printer is set from the application instead of the PDF Printer.
If you can reproduce this issue you may debug your application to see what is happening precisely when the application prints to the physical printer.
Hope this helps.
From the above description i can't be sure what is happening on your customer's site, maybe other users who faced a similar issue can give more information.
I can however tell you what could typically cause a similar situation:
1 - If your application is trying to print to the Default printer of the system and the physical printer is set as default instead of the PDF Printer.
2 - If your application prints to a sepcific printer set from inside the application and at a give time the physical printer is set from the application instead of the PDF Printer.
If you can reproduce this issue you may debug your application to see what is happening precisely when the application prints to the physical printer.
Hope this helps.
Hello,
No, it is not advisable to call SetDefaultPrinter() more often because calling SetDefaultPrinter is resource consuming.
Ideally, It is advisable to try to print to a specific printer on the system (regardless if it is the default one or not) using the available functions in your application without using SeDefaultPrinter.
Hope this helps.
No, it is not advisable to call SetDefaultPrinter() more often because calling SetDefaultPrinter is resource consuming.
Ideally, It is advisable to try to print to a specific printer on the system (regardless if it is the default one or not) using the available functions in your application without using SeDefaultPrinter.
Hope this helps.