If you need logging of everything, you might consider using SQL Server as
the back end. This gives you full logging, with transaction roll-backs, or
you could just use triggers on your tables to record whatever you want for
inserts, deletes, and updates. You can do this with the MSDE in Access. If
you choose to go that way, I would recommend simply using attached tables
rather than an ADP.
The difficulty with doing it in Access's own tables is that JET lacks
triggers. If all changes are performed through forms, you can use the form's
events to simulate it. There's an example of how to do that for inserts,
deletes, and edits in this article:
Audit Trail - Log changes at the record level
at:
http://allenbrowne.com/AppAudit.html
The article does log the entire record (not just the edited fields), since I
found auditors where happier with that complete history, particularly
because there are no real triggers and so there is always the possibility
that another change was made through another means (e.g. somebody added an
action query that does not work through the form events, and so did not get
logged.) Further, logging record deletions is the trickiest part, and
clearly that does require you to log all fields.
HTH.
--
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.
"msnews.microsoft.com" <breichenbach [ at ] istate DOT com> wrote in message
news:u2V$xOGpGHA.4236[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > Hi, First let me thank anyone who tries to help me out here.
>
> I have a medium size relational database (4 relational tables) on a
> network with about 15 users who enter and modify data. I would like to
> create a history table or multiple tables if need be, that tracks what was
> changed, by who and when. I have security in effect, so each user has
> there own userID and password and, I am able to track entries on userid.
>
> I have considered duplicating entire records when a change is made, but
> that sounds like a BAD IDEA.. I can also imagine that there may be more
> then one way to do this, so please give me your ideas....
>
> Thanks again.
|