I think the strategy depends upon need. If all you need to to know who created, data and time created and last modified by, last modified date and time, then I would add fields to table in question.
If you have a need to track who made every modification, I would put that in a sperate table. You could even track it to field level. If you are in a sesitive area (Hospital, secure setting), you might also need to track who viewed and when. Depending upon number of records, I might create a seperate table for each one to be tracked or place it in one table with table name in the the definition. You also will have to identify if you are tracking deletes and what happens if I add a record, but cancel and never save it. Hope this helps Regards, Chuck On Tue, Nov 20, 2018 at 2:59 PM Robert ListMail via 4D_Tech < [email protected]> wrote: > At a minimum, I just have the simple need of recording “CreatedBy” and > “ModifiedBy” values (username or ID) for one particular table. I do have > extra fields already in that table that could be repurposed and I would > probably add “DateModified” to that. However, that’s three fields used just > for auditing. When I look back at previous posts I see that some of you are > tracking (saving audit data for) for tables and even individual fields. So, > as I have a chance to redesign this DB, I wanted to re-think how this is > implemented. > > > So, Chip, when you have the need to store the username (or ID) of the user > that created and/or last modified a key record, do you ever have this data > in the field of the original record? I’m sure I have seen this more > commonly where the data is in the original record. I guess to keep things > normalized, you would use a related table (or a standalone table) where > each transaction that you want to remember is stored. However, with the > separate table method I suppose you would have to search this audit table > every time your detail form is loaded (assuming you want to show who > created or modified a record) and that each time the record is updated the > audit table would be getting a new record. > > Thoughts about your data audit strategy are appreciated. > > Thanks, > > Robert > > ======================= > Robert Broussard > Houston, TX > ======================= > > > On Aug 26, 2015, at 9:26 AM, Chip Scheide <[email protected]> > wrote, Re: Triggers and error handling: > > > > so my triggers tend to look like this: > > case of > > (Database event = : (Database event=On Saving New Record Event) > > trk_Last_Modified (->[Account_Postings]Created_Who) > > trk_Last_Modified (->[Account_Postings]Modified_Who) > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** -- ----------------------------------------------------------------------------------------- Chuck Miller Voice: (617) 739-0306 Fax: (617) 232-1064 Informed Solutions, Inc. Brookline, MA 02446 USA Registered 4D Developer Providers of 4D, Sybase & SQL Server connectivity http://www.informed-solutions.com ----------------------------------------------------------------------------------------- This message and any attached documents contain information which may be confidential, subject to privilege or exempt from disclosure under applicable law. These materials are intended only for the use of the intended recipient. If you are not the intended recipient of this transmission, you are hereby notified that any distribution, disclosure, printing, copying, storage, modification or the taking of any action in reliance upon this transmission is strictly prohibited. Delivery of this message to any person other than the intended recipient shall not compromise or waive such confidentiality, privilege or exemption from disclosure as to this communication. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
