Aloha, Yes. The crash did happen when accessing an array with a negative index! If that’s the only thing that causes the crash, I can be extra careful about that and do checks. Thanks for pointing this out. And yes, I wrote that serious bug. :)
As this is an internal database for our non-profits, it’s run in interpreted mode, so no compiler checking done. I do a decent amount of the programing (for the past 10-years), and use what I program. I don’t think I can use the compiler to do checking either, as tons of the code is carried forward from v1 and v2, and lots of code written without compiler declarations. Sannyasin Siddhanathaswami On Apr 6, 2017, 11:15 PM -1000, wrote: To be honest, I don't understand these problems. Our main product relies heavily on the 4D webserver on the server, for years. So far there aren't any serious problems. If there are any, we wouldn't use 4D anymore. And running the webserver on a client isn't an option for us. The only problem we experienced which causes a server crash is accessing an array with a negative index. But such things are caused by serious bugs (during development). What compiler settings do you use? Regards Lutz ********************************************************************** 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] **********************************************************************
