Several participants mentioned they use a custom user/password system and this eliminates the ability of 4D to identify and record the modifying username in the log. I have found a workaround for this. If you use your own password and user system, you can make a "hybrid" system by creating a legit 4D user account in your structure (on-the-fly as each user logs in) to match your custom user name. Then immediately use CHANGE CURRENT USER to migrate the custom user from the default 4D user name to your internally generated 4D user name. After that conversion (on the fly with each user login) all modifications in the log will be recorded with 4D user name that matches your custom user name. You don't have to pre-define these 4D users in the USERS editor. A side benefit of this is that you can see user names in the 4D Server admin window, and you can identify your modifying user with code inside triggers without having to store your custom user name in the record. There are some rules you have to follow to create 4D users on the fly, and you might run into some issues with access privileges to plugins on your freshly created 4D users. I hope this helps someone as much as it has helped me. Dan Ivy

Very interested in this topic as we are building an audit trail into our SHELL. Great topic. We used to do this another way before log files we available. That worked great but we had to do a lot of code. This is very promising for writing this with very little code, and having high confidence that everything is being audited. Questions though that would be great to be addressed in another KnowledgeBase. 1. Log file is referred to. Is that the .journal or .4BL file? 2. How do we make sure that we import each 'log' file as the log file gets imported, and eventually deleted? Comment: the Audio is hard to make out much of the time. Thanks