[AccessD] Tracing program flow

On 5/6/05, John W. Colby <jwcolby at colbyconsulting.com> wrote:
> I am designing a system to create reports to be sent to a client
> automatically every evening.  I did this before and had consistent issues
> with error handling, msgboxes in error handlers popping up and stopping the
> process etc.  This time there will be no msgboxes, but errors must be
> reported thus I am trying to build a system that can be called from the
> error handler or where a message box would pop up.  The system will log all
> such messages.  Some thoughts in no particular order.

<snippity do da, snippity day>

> Somewhere something calls the Error Handler Process.

<even more snipping>

John,

Have a look at the error handling class in the BEU. It was written to
log all errors that were handled by error handling (a bit redundant,
eh?) routines.

It may give you some ideas.

-- 
Bryan Carbonnell - carbonnb at gmail.com
Life's journey is not to arrive at the grave safely in a well
preserved body, but rather to skid in sideways, totally worn out,
shouting "What a great ride!"