[AccessD] Audit Trails

A few of comments on that solution.

Technicalities:
For an edit audit trail, storing the New Value is redundant, it is always available in either the 
primary record, in a subsequent audit entry  or in the deleted record audit record.

The Function will need to be expanded to handle Comboboxs, Listboxs, 
OptionBoxeFrames, CheckBoxes.....

Using an SQL string for the audit entry means that you will have to do  SQL escaping for 
embedded quotes.

The "biggie":
This solution doesn't work as a true audit trail - it records cancelled edits as real edits.

The only effective way to do it in Access is to  record the changes in a temporary location in 
the  Before Update procedure and insert them in the audit table in the After Update.  The 
tricky part is getting rid of the temporarily stored changes if the update is cancelled.  You 
need to make sure that and left over updates are cleared before starting to process another 
form.

-- 
Stuart
   

On 18 Jul 2009 at 14:41, Susan Harkins wrote:

> http://articles.techrepublic.com.com/5100-10878_11-6166807.html
> 
> Rocky, this will help get you started. Don't do a cut and paste from the web 
> page -- that creates a mess. There should be a download with the code or an 
> mdb file. Also, read the comments -- the readers often add little tidbits to 
> make stuff even better or more efficient.
> 
> Susan H.
>