OnPrintingComplete Event Question
I have a report that prints checks. On the OnPrintingComplete Event I
set a variable FPrinted := True. Then on close of the report, if the
user had selected to actually print checks to the printer instead of
just looking at them in the preview form, I set a field on the database
to printed (for the checks).
This all works fine except for one customer for some reason randomly
this is not working and the checks on the database are not being marked
as printed. It happens with two different users going to two different
printers, but does not happen with any other customer using the same
application (that I am aware of).
I could not think of any reason for this to fail for one customer or any
workarounds (ie a different event I should be using instead).
Can you think of anything? Thanks for your help
set a variable FPrinted := True. Then on close of the report, if the
user had selected to actually print checks to the printer instead of
just looking at them in the preview form, I set a field on the database
to printed (for the checks).
This all works fine except for one customer for some reason randomly
this is not working and the checks on the database are not being marked
as printed. It happens with two different users going to two different
printers, but does not happen with any other customer using the same
application (that I am aware of).
I could not think of any reason for this to fail for one customer or any
workarounds (ie a different event I should be using instead).
Can you think of anything? Thanks for your help
This discussion has been closed.
Comments
This is an issue that we would need to see in action to properly track it
down. There are a couple reasons that the OnPrintingComplete event might
not fire.
1. The OnPrintingComplete event will only fire if you are calling
Report.Print rather than PrintToDevices.
2. If you are loading templates, it is possible that this event handler has
become disconnected.
Perhaps you can write a test app to be sure the OnPrintingComplete event is
actually firing on their machines. If so, it may also be a data access
issue.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com