Duplex printing
Hi Guys
Delphi 7
RB 15.2
One of our clients has a printer that will print double sided on A4 paper.
They have always previously been able to go into the properties dialogue box
in the print manager window, and select the option to print ‘duplex’.
However since updating them to our latest application (compiled with RB
15.2),now when they select the Properties for the printer, it gives the
error below so that they cannot select to print to duplex.... Any ideas?
Error Message: "function address Oxd3423d caused a protection fault.
(Exception code Oxc0000005).'
Delphi 7
RB 15.2
One of our clients has a printer that will print double sided on A4 paper.
They have always previously been able to go into the properties dialogue box
in the print manager window, and select the option to print ‘duplex’.
However since updating them to our latest application (compiled with RB
15.2),now when they select the Properties for the printer, it gives the
error below so that they cannot select to print to duplex.... Any ideas?
Error Message: "function address Oxd3423d caused a protection fault.
(Exception code Oxc0000005).'
This discussion has been closed.
Comments
You say 'since updating them...' What RB version are you updating from?
Have not heard this behavior before. Does it happen with every report? Does
it happen with every printer? Can you duplicate the error on your machine?
The Report.PrinterSetup properties are used to configure the printer
settings. RB 15 introduced a new Duplex option called dpDefault that will
use the default value as specified in the Windows Printer Panel for the
printer's properties.
For your reports, check that Report.PrinterSetup.Duplex is set to dpDefault.
Also check that Report.PrinterSetup.SaveDeviceSettings is set to False.
I would also have the customer update their printer driver and test with
various printers.
Best regards,
-
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
It transpires that it was just one user that had the issue and all other
users were fine...It was that users PC! (sorry we should of course have
checked this first!)
Thanks for your help
Glenn