Bruno, That seems to be the issue. I say 'seems' because I could run the same method with the same parameters in a different context and not have a problem. And like I said this method is called very frequently. None the less when I took out the composite index the problem shifted further down the execution chain - to another similar situation with different methods but a composite index in the mix anyway.
I knew there was a problem with the composites with 4D server but this is the first time I've had a problem otherwise. Thanks again for the lead. On Sat, Jul 22, 2017 at 1:23 AM, Bruno LEGAY via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Hi Kirk, > > We recently encountered a crash on a QUERY after adding a composite > index... > We removed composite index, no more crash... > Do you have composite indexes ? > -- 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 **********************************************************************
