[AccessD] Audit Trails

Sounds like a case for a class, sinking the events for the control.

John W. Colby
www.ColbyConsulting.com


Rocky Smolin wrote:
> Just Googled Access Audit Trail and got a couple of hits.  This KB seems to
> be the most popular: http://support.microsoft.com/kb/197592
> 
> Looks like I may have to roll my own for edits - but not too hard - the
> OldValue is available in the BeforeUpdate event.  So there I could call a
> Public function, pass the form name, cycle through the controls looking for
> controls that are bound, and create the appropriate audit trail records for
> the changed fields. 
> 
> It looks, however, like I'd need a second function for the New records added
> to the table and another function for Deletes.
> 
> Rocky
> 
>  
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
> Sent: Saturday, July 18, 2009 7:40 AM
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] Audit Trails
> 
> Dear List:
> 
> I am developing an application where the user needs to record changes to
> fields in several tables - table name, field name, old value, new value,
> date/time of change, user name.
> 
> What is the best approach to this? 
> 
> Is .OldValue available after the record has been updated?  If so I could
> loop through the bound fields checking for changes and add an audit trail
> record if changed. 
> 
> It would be nice to have this audit trail function packaged in one function
> that could be called form anywhere in the app since several tables will have
> the requirement.
> 
>  
> 
> MTIA
> 
>  
> 
> Rocky
> 
>  
> 
>