Jeff,

<< I don't know the format of these tables at present, but if, as one of the
posts indicated, the real username and computername aren't available in the
UPDATES file, then adding those fields to every record that you are
interested in and setting them in the BeforePost would partially solve that
problem. >>

Correct - you can "inject" column data that you're interested in into the
updates files by simply updating them along with the other columns.

Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:B155BD27-94D1-4A7A-BBD3-2392BA2DC33B@news.elevatesoft.com...
>
>
> The only catch/decision with using published tables and update files for
> audit logging is how often should you execute a SAVE UPDATES statement to
> save the updates to an UPDATE file.  If you want fairly quick access to
> the audit log, then you'll want a scheduled job executing that saves the
> updates on a minute (or slightly higher) basis.

Since our interest in the log is mainly historical - solving problems
created by users who can't remember stuff like deleting master records
hours, days, months ... ago - there is no problem for us simply waiting for
the scheduled replication.

Cheers

Jeff
--
Jeff Cook
Aspect Systems Ltd
www.aspect.co.nz

Tim,

> 1) Execute a SAVE UPDATES
> 2) Execute a CREATE TEMPORARY TABLE....FROM UPDATES to dump the update file
> 3) Insert the contents of that temporary table into a permanent table
> that has the exact same structure
> 4) Delete the updates file.
>
> This will give you a permanent log that will serve you well for such
> purposes.

Simple, but good idea!

Uli