Justin, Thanks for the suggestion, but I already make calls to all my Compiler_Array methods, so I know it's not this...
Best, Steve ********************************************* Stephen J. Orth The Aquila Group, Inc. Office: (608) 834-9213 P.O. Box 690 Mobile: (608) 347-6447 Sun Prairie, WI 53590 E-Mail: s.o...@the-aquila-group.com ********************************************* -----Original Message----- From: Justin Carr [mailto:justinc...@geniesolutions.com.au] Sent: Sunday, July 02, 2017 9:17 PM To: s.o...@the-aquila-group.com; 4D iNug Technical <4d_tech@lists.4d.com> Subject: Re: Array Range Check Issue Hey Steve Have you initialised the array somewhere in the current process before using it here? Having a compiler declaration isn't enough - process level arrays have an indeterminate initial state, so Size of array is meaningless until you have explicitly initialised it in your code. For this reason all of our new processes start with a call to Compiler_Arrays. cheers J ********************************************************************** 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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
