>How? Seeing who made the most recent modification to a row wouldn't tell you who made the change you were interested in...
>
>
>Also used audit trail logs (populated via triggers that accessed old value/new value via the INSERTED/DELETED tables)....but in this case, the information in the core table was sufficient.

FWIW that is the approach I prefer -- put log/audit data in audit tables and leave core data tables alone.

If you want to get technical about it, audit fields in what I am calling core data tables (customers, employees, etc.) are a violation of relational theory -- the key, the whole key, and nothing but the key. (So help me Codd <g>).