Normally table triggers are the best way to deal with storing Audit information. Table triggers are the most reliable solution since they can't easily be bypassed and so the audit information is trustworthy.
The main problem with using Table Triggers is that they don't have access to the currently connected dbFront user.
That is where the "Audit Value" field property comes in: You can use that option to set a specific constant value which can contain the following dynamically replaceable values:
dbFront will set all audit fields prior to any update or insert.