no, nothing major has changed with regards to form events and scope of variables between v15 and v16.
I am not saying that running interpreted is good or bad. when you run "syntax check" the only thing it checks is typing integrity. on other words, the hundreds of errors it reports are basically all typing errors. you could track the execution sequence with debug logging (database parameter #34) or TRACE, but the order of form events is really not the issue the here. you can forgive the typing integrity and do an ad hoc patch (like you described in the original post) or face the typing issue head on, but dealing with the error as if it was because of "scoping of variable initialisation and form events" is the wrong approach, in my opinion. 2018/08/01 23:34、Noah via 4D_Tech <[email protected]<mailto:[email protected]>>のメール: Is is really 'that bad' to run in interpreted mode? My original question was simply about the scoping of variable initialization and form events in version 16. ********************************************************************** 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] **********************************************************************
