Re: Auditing thoughts...

Quoting Will Hartung - Master Rallyeist... } } We've got a client running OnLine for their application. They } want to note every time someone changes a field in their } application (i.e. who changed what field on which record and what } did they change it from). [verbosity left out]... } So, I'm looking for alternative ways of tracking changes made to } a database. Preferably something that won't be really } overbearing. Any hints will be appreicated. } In writing a medical system for my current client, I had the same dilema. Medical records can NEVER be updated, only appended to. In my system, any time someone "changes" a record, instead of doing an UPDATE WHERE CURRENT OF... I do an INSERT INTO. The first time a patient is added, the record that gets inserted get a sequence number of 1. Each subsequent "change" is just another insert with the next higher sequence number. Of course I had to make the SELECT statement intelligent enough to select the MAX(seq_nbr) record for a patient instead of selecting all of the records for a patient. When it comes to reporting this information, ALL the records for a patient are printed. Hope this sparks some ideas! DAS -- David Snyder @ Snide Computer Services - Folcroft, PA Current Release is db4glgen-3.7 UUCP: ..!uunet!das13!dave INTERNET: dave.snyder@snide.com