doesn't have to be that way; you can have a local external database on the client side. http://doc.4d.com/4Dv15/4D/15/USE-DATABASE.300-2288124.en.html
but I am slightly puzzled how LOG EVENT is in the spotlight. preemptively logging can make things more complicated, look at 4DRequestsLog.txt / 4DRequestsLog_ProcessInfo.txt. a new ID was introduced because preemptive multi-line logs can be interwoven. it wasn't necessary back in days when 4D was all cooperative. http://doc.4d.com/4Dv16/4D/16.1/Appendix-E-Description-of-log-files.300-3373556.en.html > 2017/09/26 20:41、Chip Scheide via 4D_Tech <[email protected]> のメール： > so, if this is a logging issue, will not most/all events requiring logging > pass through the server? > so logging would not/should not take network bandwidth - > log from trigger, log from stored methods, log from 'execute on server' ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
