Tom,
What we do is use triggers on insert, update and delete to write rows into one of several external databases. We went to external databases because some of the audit tables get to be quite large. We have one database each for three different inventories (raw materials, work-in-process and finished goods) plus one that takes audits for any activity against an order, including shipments. Each audit table contains columns for the data we're interested in auditing, and includes timestamps, userids and such. For update transactions we write a before record and an after record. The audit databases are SATTACHed to the main database. We use Oterro for the ODBC connection. Emmitt Dove Manager, DairyPak Business Systems Evergreen Packaging, Inc. [EMAIL PROTECTED] [EMAIL PROTECTED] (203) 643-8022 From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Frederick Sent: Tuesday, July 29, 2008 1:47 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Transaction logs Is there a preferred method of tracking changes users make to database info? We currently track who was the last user, computer used, date/time to make changes to rows in a table. While this works great, it does nothing to track who changed individual fields within the row or what was changed. It would be very common for three users open a form for Table INFO, each change 1 of 20 different fields, and all we would know was who was the last person at INFO. We are looking at several options (i.e., load row into variables, delete unchanged rows, convert data to text, and append to a TRANS table with the user ID info). Is this a case of paranoia on our part? Yep, but we can also see a bunch of coming performance problems if we do nothing. Is there a sample in R:Base or a basic procedure we should follow? This feels like a potentially large project but needed. Tom Frederick Elm City Center 1314 W Walnut Jacksonville, IL 62650 Off - 217-245-9504 Fax - 217-245-2350 Email - [EMAIL PROTECTED] Web - www.elmcity.org
