I’m liking “Get call chain” which I’m only seeing now that we are working on v18. Much of our error handling code creates an automatic log entry into a table in our database, it was trivial add a call chain to the log so we can see the pathway to the problem.
However, I have to say that I’m a little disappointed that the function name does not include the table when including a form object method. I mocked up a (admittedly awful) minimal example where I open a related form from a master form. As you can clearly see, 4D’s debugger can see the table, but that knowledge is not included in “Get call chain”.
The problem comes when one table form opens a table form from a different table. This is a very normal workflow for us, since our database is very old, and much of it uses the “input form” “output form” workflow.
Assume that “SetCallChain” is my error handler. As you can clearly see from the image, there is no way for the error handler to know the table source of the first form. I could probably wire up some sort of a stack that holds the forms being opened, but that kind of defeats the purpose behind calling a call chain handler in the first place.
I guess I should have asked; is there something I can do? Or am I stuck without the knowledge of the originating table?