>>Thank you for the suggestion. As I mentioned in my message to Kevin, right now my priority is to get the audit log as simple as possible and getting to SQL backend as soon as possible :)
>
>Understood and on the priciple of KISS full ACK. But implementing such 1 or 2 "fingerprint" fields in a base class is still much less work than an audit trail.

The purpose of audit trail is not as much in the trust issue (though that's also one of the aspect), it's more on the history side. A fingerprint, or any other field with a similar purpose, shows only who changed the record, and possibly when - but that's only the last change. A full audit trail shows all the changes as they happened, from the initial insertion of the record until today, with identities and datetimes. Including the deletion in the end, if any.