[AccessD] Audit Trails

ROTFL.  A class is not a hammer.  But for those without classes...

John W. Colby
www.ColbyConsulting.com


Stuart McLachlan wrote:
> To a man with a hammer, everything looks like a nail <g>
> 
> I certainly wouldn't try to trigger an audit trail at the control level. The logical place is at the 
> time you insert, update and delete a record.   
> 
> For the insert, you don't need to store any info about the record other than its PK.
> 
> For the delete, you need to store all fields for the record whether they are displayed on the 
> deleting form or not.
> 
> In neither of these cases do you need to iterate through controls.  It's only the Edit audit that 
> needs iterate through the fields exposed to controls on the editing form and record which 
> ones have changed.
> 
> There is a lot to be said tor using three different audit tables for the three different cases.
> (That's exactly the way I've done it in the past in SQL Server using triggers).
>