Jody, Right, but what I'm seeing is a client side process which has an error handler installed. Running a method with EOS an error is blocking the server with the 4D native error handler. Even though the server has an error handler installed. This is following the what's in the docs:
"ON ERR CALL is usually placed in the startup database method of an application, in order to handle errors for this application." ​Seems to suggest that would be the method called absent some specific method and instead of the native 4D error handler. So that's why I expect the server to use the handler I install there. It seems like this is something specific to methods running EOS because I've installed an error handler on both the server and the client process but the 4D error handler is winding up with the call. On Fri, Jul 7, 2017 at 2:52 PM, Jody Bevan via 4D_Tech <4d_tech@lists.4d.com > wrote: > On Error Call is process based. Therefore each process needs to call it. > > -- Kirk Brooks San Francisco, CA ======================= *The only thing necessary for the triumph of evil is for good men to do nothing.* *- Edmund Burke* ********************************************************************** 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 **********************************************************************
