Murphy’s Law is commonly summarized as “anything that can go wrong, will go wrong”. This can be applied to anything and everything from walking and tripping or in this case, a software application encountering an error. With any complex software application, including 4D, many various factors can cause an issue to occur.

When 4D encounters an issue, it will generate an error dialog. The error dialog is helpful in general cases for the developer. However, for a deployed application it may not be enough to properly inform the user of the issue and relay the problem to the developer. 4D provides the ability to implement custom error handlers to tailor the error-handling process to fit the needs of the developer and the users. This Technical Note will go over the process of using a custom error handler. Suggestions on what an error handler should do will be provided. An example database including the full example error handling methods will also be provided as examples of the suggested implementations.