Lutz, Agreed. This is a db that started back in the '90s and has an extremely complicated scheme of arrays to handle the menus. Then over the years other devs needed to change or add some functionality and, I think, rather than try to unravel what was existing added on more menu management for their purposes. This resulted in a very complex web which I upset by making a change unrelated to menus at all. I'm going to take a little time and see if all of that is even necessary any longer. The tools available for menu management are much better now. When I found myself trying to pull a tech note out of ACI FTP from 1996 so I could read up on how menus were managed back then I realized I may be going about this the wrong way.
On Tue, May 23, 2017 at 12:10 AM, Epperlein, Lutz (agendo) via 4D_Tech < 4d_tech@lists.4d.com> wrote: > My first favorite cause of crashing compiled databases is a negative array > index. That's very reliable, hard to find. > The best way to avoid such problems is to code defensively while handling > arrays. > -- Kirk Brooks San Francisco, CA ======================= *The only thing necessary for the triumph of evil is for good men to do nothing.* *- Edmund Burke* ********************************************************************** 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 **********************************************************************