The form's Dirty event fires when you *begin* to make a change to a record.
It does not exist in older versions of Access, and in some of the more
recent versions, the event does not fire if the record is dirtied
programmatically. It is therefore less than ideal for this kind of task.
The form's BeforeUpdate event fires at the last possible moment before the
record is saved. This event works consistently in all versions of Access. It
is most commonly used for record-level validation, but is also idea for this
kind of task. Particularly if you want to save the date and time of the last
edit, using the last possible moment before it is saved makes the best
sense.
It is possible to use the form events to write an audit trail of all
inserts, edits, and deletes. This involves using lots of the form events,
but if you ever need to do that, the details are here:
Audit Trail - Log changes at the record level
at:
http://allenbrowne.com/AppAudit.html
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
<philmgron@hotmail.com> wrote in message
news:1150386579.203752.203810@f6g2000cwb.googlegro ups.com...[color=blue]
> Thanks alot worked like a charm:) you ve been a great help.
>
> One other question if i may, what is the event on Dirty, as i have been
> reading the forums and i think i have come to an understanding that it
> means that the form has had a change made to it?[/color]