This one in particular may take awhile. It took about 16 days for us to see the issue for the first time. Who knows when it will happen again? So more people watching for this issue should shorten the amount of time needed to get this identified.
-- Jeffrey Kain [email protected] > On Sep 15, 2017, at 3:07 PM, Tim Nevels via 4D_Tech <[email protected]> > wrote: > > Bugs in 4D don’t fix themselves by simply talking about them here. If you are > expecting 4D staff to read a post on the iNUG and then run into the next room > and say “we have a bug in 4D we need to look at”, I think you are expecting > too much. Opening a tech support case for the bug is the first step in > getting it worked on and fixed. ********************************************************************** 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] **********************************************************************
