Thank you both for the speedy replies! Unfortunately this inherited application IS running in interpreted mode and has hundreds of errors that would keep it from compiling.
As time permits we will occasionally revisit the compilation errors and work towards a compiled version (but we have not made it there yet). Consequently, Typing Generation and Syntax Checking both fail (since this application had never been written with compilation as a goal) Do you have any other suggestions? 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. On Tue, Jul 31, 2018 at 3:25 PM Timothy Penner via 4D_Tech < 4d_tech@lists.4d.com> wrote: > In addition to what has already been said - > > Using a compilation path of "All variables are typed" is highly > recommended: > http://kb.4d.com/assetid=50223 > > -Tim > > > > ********************************************************************** > 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 > ********************************************************************** ********************************************************************** 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 **********************************************************************
