Hi Jason,
Sorry about the delay in getting back to you, I was ill for a few days last
week.
Two techniques you can try are to check the form's Dirty property before
displaying any message, and do not display the message if no changes have
been made (the Dirty property is False) and/or display a warning message
telling the user about the potential problem, but don't prevent the user
from leaving the text box. You may need to test again in the BeforeUpdate
event, but you can put the code in a procedure that can be called from both
events, rather than repeating all the code in both event procedures.
--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com
The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.