I should have mentioned that. I do have an ON ERR CALL running. When in interpreted mode, it catches errors. This does not seem to be occurring when compiled. I would think that in the least it should present no standard error dialog due to the ON ERR CALL handling method.
I will try to temporarily upgrade to 17R6 and see what happens. Thanks for your input. On Sep 9, 2021, at 2:19 PM, John DeSoi via 4D_Tech wrote: > I would setup an error handling method (ON ERR CALL) and use GET LAST ERROR > STACK and see if it provides more information. If you could update to at > least 17R6, you could use the Get call chain command to see exactly where the > error is. > >> On Sep 9, 2021, at 11:05 AM, Eric Asadoorian via 4D_Tech >> <[email protected]> wrote: >> >> Where would be a good place to start looking? Has anyone had such an >> experience before? Is there a way to identify more clearly what code is >> executing when the error appears? > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > New Forum: https://discuss.4D.com > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
