Audit trail of masterfile changes

[Chris Sharman]

>The audit file option doesn't seem to help as it only stores an after image
>of all the fields changed.

The reasoning behind this is that the old values are in the previous audit of
the same record: if you allow users to inspect the audit history they should be
able to see which fields changed at each step.

This halves the size of the audit and avoids the need for comparison routines.

If you really want to do it as a textual log from Quick, probably the field edit
procedures are the best place: add the changes to a char temp, and write that
away during the update. Edit is the last chance you have to use oldvalue(), and
it only gets called for the fields the user changes.

Chris
______________________________________________________________________
Chris Sharman			Chris.Sharman@CCAgroup.co.uk
CCA Stationery Ltd, Eastway, Fulwood, Preston, Lancashire, PR2 9WS.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.