Hi Chuck, I think in this case, this makes sense. I never thought about tracking all record updates or going further… all updates on chosen fields. I recall in the past that other developers that cared about such things had a 3-4 fields added to each record and could easily see who created and who updated and when…. When I looked at some of the previous (more recent) NUG messages I see the where some people needed the granularity of field level or they need to know about every update (not just creation/modified). Thanks for chiming in. 4D is an amazing set of tools but sometimes you want to consider design ideas that have been successful in other projects.
Thanks, Robert ======================= Robert Broussard Houston, TX ======================= > On Nov 20, 2018, at 2:12 PM, Charles Miller via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > 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. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
