Event to use aftera page has been printed in report

[Bob]

Still using Access 97 :-( but I need to write some code that does an update
to a field in a table but only AFTER the page has been successfully printed.
The report is typically multi-page, so I can't wait for the report to be
completed, I need it done after each page.
I find a page print event, but that occurs before the printing is actually
started, so I use it to put in an incremented counter in a non-bound field
that needs to be printed.
But I can't find a page after printed event which would seem the obvious
place to look, but maybe there's another way.

Any help would be greatly appreciated.

Bob

 

[Larry Linson]

Put that code in the On Print or On Format event of the Page Footer. Create
a Page Footer, if you don't have one.

Larry Linson
Microsoft Access MVP

 

[John Vinson]

only AFTER the page has been successfully

Well...all that any software on the computer can know for sure is that
the page was sent to the printer. It can't determine whether the
printer jammed, or ran out of toner on that page, or...

John W. Vinson[MVP]

 

[Brendan Reynolds]

As John says elsewhere in this thread, there isn't any reliable way for
software to detect that a page was *successfully* printed. I've successfully
handled this situation in the past simply by prompting the user with a 'Did
the report print successfully?' message box in the Close event of the
report. If you're not sure that you can trust the users to answer the
question accurately, I recall someone (Arvin? Dev?) describing a technique
that involved printing a random number in the report footer and requiring
the user to enter the same number as evidence that the report printed.

 

[Bob]

Thank you all

Bob

As John says elsewhere in this thread, there isn't any reliable way for
software to detect that a page was *successfully* printed. I've
successfully handled this situation in the past simply by prompting the
user with a 'Did the report print successfully?' message box in the Close
event of the report. If you're not sure that you can trust the users to
answer the question accurately, I recall someone (Arvin? Dev?) describing
a technique that involved printing a random number in the report footer
and requiring the user to enter the same number as evidence that the
report printed.