audit log on normalized data

Hi,

We have a database. What make changes to tables.

We have persistent objects that map one to one with database tables.

When a change occurs to some high level things in our system, we want
to log these changes in a meaningful way. So lets say the user sets the
"Customer First Name" on an order. We want to record that the user has
set the "Customer First Name" on order 123.

Our database (and therefore our persistent objects) is normalized so
that it is often difficult to figure out what particular high level
thing a row is associated with. For example if someone changes the
"First_Name" field of the Name table, they might be changing the
"Customer First Name", or they might be changing some other field in
one of the 30 odd places our name table is used.

What's a good way to create a meaningful audit log in this situation?
Any suggestions? Any drastic solutions? Simple solutions? Anyone had a
similar experience?

Thanks,

Jon Paugh

.

Relevant Pages

  • Re: audit log on normalized data
    ... We have persistent objects that map one to one with database tables. ... then what you are describing is a RAD USER/CRUD problem that has nothing to do with OO development. ... So lets say the user sets the "Customer First Name" on an order. ...
    (comp.object)
  • main form disappears after paste-append action using VBA
    ... I have an access 2003 database in which I built the opportunity to make ... a list of data in Excel and paste it later in the access-database. ... MsgBox "You have to select a customer first! ...
    (comp.databases.ms-access)