John, I type all variables, but I’ve seen this with SET QUERY DESTINATION as well in some test, maintenance and “throw-away” code in which typing may or may not exist. Do you know any other commands that have this issue in R5?
---------- Jeff Grann SuccessWare, Inc. > On Jan 19, 2018, at 12:36 PM, John Baughman via 4D_Tech > <[email protected]> wrote: > > Jeff, > > I have deployed R4 to 2 clients several months ago and did not seen any > problems. > > I have now deployed R5 this month and so far so good. > > One issue with R5 is that running interpreted typing is an issue with a few > commands such as SET QUERY DESTINATION (into variable;myVar). Unlike previous > versions myVar will throw an error as myVar will be undefined unless it has > been previously used or explicitly typed. Of course this is not a problem if > you are running compiled or otherwise disciplined to have everything typed. > > John Baughman > Kailua, Hawaii > [email protected] ********************************************************************** 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] **********************************************************************
