> On Sep 14, 2017, at 7:05 PM, Tim Nevels via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > This is a big problem that must get addressed and fixed or it will do harm to > v16’s reputation. I was planning on upgrading one of my clients to v16 in a > few months. That is not going to happen now. I can’t afford to have my Stored > Procedure randomly stop running. So v16 upgrades for me are never going to > happen until I hear this bug has been fixed. This could spread to others and > give v16 a very bad name. Nobody wants that. Especially 4D Inc.
Agree. I'm also waiting to be convinced that 4D Client performance with the new network layer on on par with version 15. It seems the majority of comments have been negative. It would be great to hear some success stories for 64bit 4D Client, especially Mac. John DeSoi, Ph.D. ********************************************************************** 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 **********************************************************************
