Sannyasin, I took Bruno's suggestion and deleted the composite index for these two fields. After that I was still getting a crash but it had moved further down the execution chain. So I just deleted all the composite indexes.
That seemed to fix the problem. On Sat, Jul 22, 2017 at 2:20 PM, Sannyasin Siddhanathaswami via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Code looks fine to me. Is it possible $1 or $2 is accidentally the wrong > type (aka, not text). I’ve had fun crashes by accidentally passing an array > that should have been just text… > -- 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 **********************************************************************
