From: George Applegate on
I have a payroll record data base - records the employee, date, time,
in or out of when they punch in.

I am going to have to allow some users the ability to delete, add or
even change records.

Is there an easy model to follow of how I can somehow track when
changes are made and what those are?

For instance, can I somehow write copies of any records that are
changed to another table? Can I write copies of any record added to
another table or copy any record deleted to another table? If a
record is changed, it'd be nice to have a "before" and "after" view.

I am sure someone has run across this issue before and am wondering
how it might best be resolved.

thanks for any suggestions.
ga

George Applegate
gappleg8(a)nospam.fmctc
From: Golfinray on
Recording the date and time is fairly easy. Add a Last Updated field to the
table and then add to your form. Go into the lastupdated text box on the
form, look at events, and in the beforeupdate event type
Me.last_updated=now()
For who updated, that is more complicated. See www.allenbrowne.com for a
solution.

"George Applegate" wrote:

> I have a payroll record data base - records the employee, date, time,
> in or out of when they punch in.
>
> I am going to have to allow some users the ability to delete, add or
> even change records.
>
> Is there an easy model to follow of how I can somehow track when
> changes are made and what those are?
>
> For instance, can I somehow write copies of any records that are
> changed to another table? Can I write copies of any record added to
> another table or copy any record deleted to another table? If a
> record is changed, it'd be nice to have a "before" and "after" view.
>
> I am sure someone has run across this issue before and am wondering
> how it might best be resolved.
>
> thanks for any suggestions.
> ga
>
> George Applegate
> gappleg8(a)nospam.fmctc
>
From: Linq Adams via AccessMonster.com on
Allen's site is humongeous, so here's the URL for the exact page for his
Audit Trail hack. As Golfinray hinted at, though, this is not going to be
easy!

http://allenbrowne.com/AppAudit.html

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

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access/200807/1