What you have asked might be difficult to answer. The sample code I gave
should fire up the BeforeUpdate event of your control even if the auto-fill
is in the new record and if the control is being edited it should fire up the
control event. But I'm not certain of how your auto-fill works like - does
the record is save first? If it is, it should work.

The best way to learn is to do a trail and error.

oldblindpew wrote:
Thanks for reading and replying. I fear I've offended the gods as some of my
recent questions have met with silence.

When a new record is added via my form, some of the fields are populated
from other tables, and this is the data I wish to protect. The key question
is whether the Before Update event will interfere with the addition of the
new record and automatic population of certain of its fields. Should be easy
enough to try and see. I have not yet needed the different events other than
On Click.

In the past I've created a separate form for updating vs. adding. I'm
thinking one cannot simultaneously allow and disallow editing in the same
form. Perhaps this is why a traditional approach uses modes: Add, Delete,
Update, and Browse. Obviously I have more to learn.

Thanks Again,
Pew

--
Please Rate the posting if helps you.

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...forms/201002/1