> On Oct 3, 2017, at 3:56 PM, Dennis, Neil via 4D_Tech <[email protected]> > wrote: > > The ones that I have submitted that are reproducible I include a small > database demonstrating them. The bug is filed, I get email notifications as > it is updated and accepted, then I get an email telling me it is in one of > the nightly builds and I can test it.
This is the key difference. I spent about an hour this morning looking at this again and could not find any cause or reason. If I had, I would have opened up a tech support case. > > The one that I reported that I could not reproduce, I had constant emails > between me and tech support until they actually figured out how to reproduce > it then sent it on to the engineers. Yes, and this what I don't have time for. My only goal for today was to update my observation that I had not seen this issue previously in 16.2. The effort for 4D to follow this list (assuming they already do) is tiny compared to filing a bug without a reproducible test case. If the information on this list is not helpful to 4D in any way, they are free to ignore it. I find observations posted by others to be helpful and informative. 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:[email protected] **********************************************************************
