Mike,

One of the things that we do is place a userkey in every table and every update of a record includes the userkey of the person making the change (we get this when the user logs into the system). Consequently, the userkey would be included in the triggers that update your Audit tables and from that you can see who made the change.

The only downside to this methodology, is that if tables are modified from outside your application, userkey may or may not be saved.

~~Bonnie



>Hi Kevin,
>
>Thanks for enlightening me. I have a few question though regarding the use of Update Triggers in Audit Trail.
>
>1. If the system does not use Windows Authentication and maintains its own list of users, how can I record the user who edited the record?
>
>2. A module like Purchase Order contains 2 or more related tables, how can I audit that the records in table1 and table2 were edited in Purchase Order Module and were audited by user1?
>
>Thanks in advance...