There may be a better approach but can't say based on the info. Having beforeUpdate events on a form as well as all of its controls seems like overkill.
I've never tried, but here's a notion
- declare a form level variable (Boolean?) and set it as the very first button code line. In form update, check that variable and Cancel = True if it has the right value.
However, being able to cancel the form level event seems dangerous to me and implies that if it's sometimes unnecessary, it is not of much use. It will fire if the user attempts to leave the record, so why not just have one or the other? Maybe more info as to why you have both would allow for more focused answers.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.