[AccessD] Audit Trail Suggestions

[Stuart McLachlan]

With a SQL Server BE, you should set up After Update  triggers on the tables.

See for example:
https://msdn.microsoft.com/en-AU/library/ms186329.aspx
and
http://www.mssqltips.com/sqlservertip/2342/understanding-sql-server-inserted-and-deleted-ta
bles-for-dml-triggers/



On 14 Mar 2015 at 17:21, David Emerson wrote:

> Hi Team,
> 
> Looking for ideas for implementation.
> 
> Access 2010 FE, SQL 2008 R2
> 
> A client wants to keep track of some fields in some tables when they
> are changed.  There are over 50 tables involved and anywhere from 3 to
> 30 fields per table.  The tables and fields are predefined.  Most of
> the data changes will be done via Access screens but there are some
> fields that are changed through code
> 
> When a field value is changed they want to store in a log table date,
> person making change, old value, new value.
> 
> Looking for ideas of how others might have tackled this type of
> problem before.
> 
> Regards
> 
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
> 
> 
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>