Brook:
This is kind of an age old problem. The issue is, what if the user preview
the report, but doesn't print it? Do you still want to update the field?
Secondly, if the print fails (e.g. low toner,) do you still want to update
the field (assuming that the field is what pulls data into the report....
Its best to have a separate process for updating records, possibly run from
a form, where you have a separate preview button and a separate print button
and only after the print job is sent do you query the user about updating
the records (and you use an update query to update the rows in the table
based upon the records selected, of course this also gets a little nasty if
you have multiple users using the same reporting process simultaneously,
wherein you need to also think about control). For this to work properly
you normally create a separate menu bar and tool bar for your target report
that doesn't contain the print option. Then set those into the report's
properties so that when the report is previewed you can't print it. PITA,
but its about the only way it works (effectively that is)