Developers may face runtime errors from time to time. Indeed, tracking down and fixing these errors are part of software development. Finding the root cause of an error can be difficult if the end user does not communicate the full details of the error; it is therefore important that the developer have a way of logging the errors and the necessary information required to determine what happened. This task is made a lot easier with the introduction of “Get Call Chain” command in 4D v18. This Tech Note introduces the new Get Call Chain command along with an example error handler that can help facilitate further analysis. Also included with this Tech Note is a parser for the logs created by the example error handler.

Download Complete Tech Note: Tech Note Document