>>If I understand your question correctly. I have a table in the SQL Server and a class in the app that creates a record in this table for every other table change. Logging who made the change, what time, and specific change. Then, I have a bunch of reports that show any changes done to a table. Therefore, a user or an admin person can view complete audit trail of change. If I misunderstood your question, ignore my input.
>
>Those are certainly very important - using Triggers or other features in SQL Server to capture who changed what and when.
>
>The auditing requirements I've seen over the last several years have veered a little away from that (for reasons I don't quite understand), and more towards automated deployments, making sure developers can't deploy to production, making sure all report/database jobs are funneled through a special account.
>
>Auditing requirements can be a real task - especially when you work for a public-traded company. And rarely can you debate with them - it's sometimes the old "find out what they want, make those things happen, and they'll usually go away" :)

Just for the record, I don't use Triggers to log changes. And as far as viewing the log file - via a VFP report - this feature can be set on/off by the user of the application.