T
TC
I don't have Access here to check, but I believe that the cancel & me.undo
would just undo the value entered in that field. I don't think it will undo
the creation of an unsaved new record. So you are still positioned on a new
record, no?
Do you really want to automatically >discard< the unsaved (blank) new
record, when the value entered in that field is already on file? That's a
bit non-standard, IMO. Normally you would issue a message, cancel the
beforeupdate, but >not< Undo. Then the user can amend the value & try again,
or press Esc a few times to discard the unsaved new record.
HTH,
TC
would just undo the value entered in that field. I don't think it will undo
the creation of an unsaved new record. So you are still positioned on a new
record, no?
Do you really want to automatically >discard< the unsaved (blank) new
record, when the value entered in that field is already on file? That's a
bit non-standard, IMO. Normally you would issue a message, cancel the
beforeupdate, but >not< Undo. Then the user can amend the value & try again,
or press Esc a few times to discard the unsaved new record.
HTH,
TC