R
Randall Arnold
If I can successfully temporarily disable the popup menu of the report and temporarily hide the application menu without it affecting the application at large then here is my solution: In the report's close event, I will first ask the user if they want to print. A "yes" response will fire the Print action and then lead to my verification code. That's the best way I can think to do this. I don't like custom menu bars because they (for some reason I can't fathom) lack the ability to be attached to the report itself and thus don't seem intuitive to the user (trust me on this one). Plus the one time I tried it, the application menu wasn't restored automatically when the report closed. I don't like that
Randall Arnol
----- SA wrote: ----
Randall
Unfortunately, this is an historic and ongoing problem for Access reports;
there's really no way to work around it other than the suggestion noted
below. The issue is that there really is no "Print" event. Even if you
use the OnActivate event to denote when the report is previewed, then the
user can still send the report to print from there and no addition event is
fired
The only real way to assure that you know when a report is printed vs
previewed, is to a.) create print and preview buttons on your form that
calls the report. only run your update code from the print button. b.)
create custom tool bars and menu items to use with your report that elminate
the standard Print option so that when a report is in preview, the user
can't print from there, i.e. they have to close the report to print (from
your form to print) or create your own Print function in a general module
that your custom toolbars and menus call when the print item is selected,
and run your update code after the print command if there's otherwise no
error encountered
Its a hack, but really that's the only way to do it. On Activate just
won't do the trick
Randall Arnol
----- SA wrote: ----
Randall
Unfortunately, this is an historic and ongoing problem for Access reports;
there's really no way to work around it other than the suggestion noted
below. The issue is that there really is no "Print" event. Even if you
use the OnActivate event to denote when the report is previewed, then the
user can still send the report to print from there and no addition event is
fired
The only real way to assure that you know when a report is printed vs
previewed, is to a.) create print and preview buttons on your form that
calls the report. only run your update code from the print button. b.)
create custom tool bars and menu items to use with your report that elminate
the standard Print option so that when a report is in preview, the user
can't print from there, i.e. they have to close the report to print (from
your form to print) or create your own Print function in a general module
that your custom toolbars and menus call when the print item is selected,
and run your update code after the print command if there's otherwise no
error encountered
Its a hack, but really that's the only way to do it. On Activate just
won't do the trick