> Normally, it's a good idea to check if the record needs to
> be saved.
>
> If Me.Dirty Then Me.Dirty = False
I do that, too, but as far as I can tell, it just shaves some
infinitesimal amount of time off the statement if the form happens not
to be Dirty.

Signature
Dirk Goldgar, MS Access MVP
www.datagnostics.com
(please reply to the newsgroup)
Marshall Barton - 20 Mar 2007 23:35 GMT
>> Normally, it's a good idea to check if the record needs to
>> be saved.
[quoted text clipped - 4 lines]
>infinitesimal amount of time off the statement if the form happens not
>to be Dirty.
I was wondering about that. Don't have time to set up
whatever experiments would be needed to verify that the
record isn't saved even when it's not dirty. Probably a
Before/AfterUpdate MsgBox would ... That's too easy to avoid
with the no time excuse. OK, the BeforeUpdate doesn't fire
unless the current record really is dirty and I can't
imagine any other side effect. Gotta have a little faith
that the developer that added the dirty = false feature
would do a decent job. Thanks for the kick in the butt Dirk
;-)
--
Marsh