From: Linq Adams via AccessMonster.com on
Sorry, that should have said

When you press <F7>

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via http://www.accessmonster.com

From: Arvin Meyer [MVP] on

"Linq Adams via AccessMonster.com" <u28780(a)uwe> wrote in message
news:a5a5394a241ba(a)uwe...

> Date stamping a record should ***always*** be done in the
> Form_BeforeUpdate
> event! This event will ***always*** fire when a change has been made to
> the
> data, regardless of how that change was made, and the record is saved,
> thru
> moving to a new record, closing the form, or an explicit save. If spell
> check
> is run and no change is made, Form_BeforeUpdate will not fire and the date
> stamp won't change.

I prefer to alter data after a change is made. I use BeforeUpdate to write
to other fields, like adding a username and datestamp to a record before
saving it. Using BeforeUpdate is usually safe, but it is possible to stick
yourself in an endless loop from which a Ctl+Alt+Del is the only way to
extricate oneself.


From: cmk7471 on
That was exactly what I needed! Thank you!

"Linq Adams via AccessMonster.com" wrote:

> "...I'm not using any code to run spell check."
>
> Sure you are! When you press <7> you're using code that built into Access!
>
> Control events, as you've found out, don't fire unless you ***physically***
> enter data, either by typing it in or pasting data into it.
>
> Date stamping a record should ***always*** be done in the Form_BeforeUpdate
> event! This event will ***always*** fire when a change has been made to the
> data, regardless of how that change was made, and the record is saved, thru
> moving to a new record, closing the form, or an explicit save. If spell check
> is run and no change is made, Form_BeforeUpdate will not fire and the date
> stamp won't change.
>
> --
> There's ALWAYS more than one way to skin a cat!
>
> Answers/posts based on Access 2000/2003
>
> Message posted via http://www.accessmonster.com
>
> .
>