On Oct 25, 2017, at 3:45 PM, Timothy Penner <tpen...@4d.com> wrote: > I just want to add that one of the main benefits of the Forums > (http://forums.4d.com) is that it is also used by the 4D Engineers and they > do monitor, read, and participate in the discussions. So posting on the > forums could give you the opportunity to discuss this directly with the > Engineers. This participation is one of the main reasons why Feature Requests > are handled on the forums (as described here: http://kb.4d.com/assetid=76725).
Hi Tim, I know it, I know it. But me and so many other 4D Developers are old dogs. And you what they say, “hard to teach an old dog new tricks”. Particularly when the bones 4D Forums offer taste so terrible. In other words. It’s just to darn easy to deal with the iNUG email setup, and it is a big pain-in-the-ass to deal with how the 4D Forums work. Takes nine million clicks to view everything and to find anything. Here you just glance at emails and you get all the info you want. You want people to use the 4D Forums, make it taste so good we won’t want to use old fashion emails any longer. Here’s a radical idea, create an email interface/adapter for the 4D Forums so you don’t have to use that horrid web interface. You just send specially formatted emails and it inserts them into the 4D Forums. And when someone replies on the 4D Forums it send out an email. Then there would be no excuse to not participate in the 4D Forums. Too bad nobody in France is smart enough or motivated enough to do something like that. :) >> Somebody needs to forward this email chain to 4D engineering. Hopefully Tim >> Penner can do this and get 4D engineering motivated to stop waiting for a >> demo database that reproduces this problem and have somebody go do a code >> review looking for something that doesn’t look quite right. > > I wish it were that simple. I see some theories about what's causing it but I > don’t think anyone has nailed down a concrete explanation or reproducible > test that could be used in a bug report. Sorry, but I cannot file a bug > report for something this vague. Although, to be clear, I have tried running > some tests to see if I can provoke the issue and I never saw it (so > technically if a bug was filed with the information we currently have it > could be marked as 'verified and non-reproducible' by tech support). I totally understand that. I just want to help in any way I can to get this resolved. Right now I have no v16 users. I was planning to do an upgrade but this put a stop to that. No way. I’m steering clear of upgrading to v16 until I hear that this problem has been fixed. And that’s what I tell anyone that asks me about upgrading to v16. If you don’t use Stored Procedure, go ahead, but if you do you are asking for trouble. If it is affecting Jeff and Cannon, it could effect anyone. This is not a 4D developer coding error, this is a 4D bug! I’m a big user of Stored Procedure and I don’t need the headache of them acting up when everything is completely stable now. And it’s a bug I can’t even implement a work around for, other than to manually monitor all server every single day and executing RESUME PROCESS commands manually when I detect an issue. I’ve got work to do. I’m not going to become a server babysitter. And the last thing I want is calls from clients saying “that 4D upgrade you installed is sure causing problems, why don’t you fix it”. And my only reply is, “I can’t, live with it”. I’m sure you understand that. Tim ******************************************** Tim Nevels Innovative Solutions 785-749-3444 timnev...@mac.com ******************************************** ********************************************************************** 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 **********************************************************************
