Why You Need a New Error Handler

Error handling is an integral part of application development. Unless you are like myself and never release code with bugs 🙂 , the need for clients to tell you what's wrong is important.

I've seen a number of error handlers in the past, dating all the way back to Pat Adam's famous FP2ERROR routine (back from 1991).

Most systems log their errors and then pick them up as part of a diagnostic push. Unfortunately, reporting these errors back to the developer require some effort by the client.

Doug Hennig has introduced a new VFPX project for adding easy error handling and reporting. While it does include a few dependencies, it offers a nice support-centric dialog for clients to report errors.


If you AREN'T getting automatic feedback from your clients when they get an error, now there's no excuse.