On Thu, Oct 26, 2017 at 7:45 AM, Timothy Penner via 4D_Tech < [email protected]> wrote:
Thanks for chiming in. Given the number and nature of the people reporting this bug, it's clearly a real bug. Can you give us some insight into what efforts 4D is making internally to track this down and fix it? The way I interpret your remarks is "We're waiting for customers to figure out what the problem is." Is that a mis-characterization or even a totally off-base reading of your message? Is there an *active* effort within to track down this particular problem? Thanks. ********************************************************************** 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] **********************************************************************
