Paul wrote:
I've put the code that evaluates the user's authorization status and sets
AllowEdits in the form's Load and Current events, so I'm thinking the only
way it could be dirty would be if someone else was in the process of editing
the record when the user brought that record up. Is that correct?

If so, it's not likely to be a problem, because of the large number of
records, small number of users and low frequency of edits.


No. The form would only be dirty if you allowed a user to
edit a value or you have code that sets a value in the
current record before you try to lock it. If this could
happen, it would be a flaw in your logic or code.

For example, setting a value in a bound control in the
Current/Load event before setting AllowEdits. (This
scenario should probably be considered a bug even without
the use of AllowEdits.)

Two different users/forms simultaneously editing a record is
a different question.

--
Marsh
MVP [MS Access]