Hmmmmmmmmmmm,
A bit of work to detect that 'it' was ACTUALLY printed, since Ms. A. doesn't usually notice the difference between "print" and "printpreview", except for the device the information is sent to.
On the other side, once the overall report is 'correct' (from the design perspective), there is usually little reason for 'printpreview' in the situation as I undestand your description.
So, I would just assume that generation of the REPORT was sufficient to identify the record / report printing and use the report recordsourct to 'immediatly' make the table change (e.g. set [printprofile] = False)
For a more robust soloution, you could use much the same approach, but replace the boolean [printprofile] with a [printdate] (as date?) and fill in hte date time a profile was 'printed'. If a new profile was necessary, just set the [printdate] to null.
MichaelRed
m.red@att.net
There is never time to do it right but there is always time to do it over