Not clear on what you mean by "logging to register the processes"; Does each
procedure write to a sheet or metadata that it ran?

"Patrick Molloy" wrote:

add a new class, call it say clError , then process has an error handler that
(1) creates a new clError object and save it to a collection.
The clError should contain the details - process name, error number, error
message and whatever. the collection should be PUBLIC

at the end of the process, you can interrate through the collection or error
objects to see what happened.

This isn't normal imho. Almost all the investment banks that I work for use
logging extensively to register the processes. This makes it easy (readign
the text file) to see where the process is, and to review any errors





"headly" wrote:

The message box stops execution and requires the user to respond; if the
process generates 100 errors I can't have someone babysit it for 30-60
minutes and click OK to each message, I just want to continue processing and
log errors.

"Spreadsheet Solutions" wrote:

Headly;

Maybe the simplst of things you can do within each of these small procedures
is run an error handler with a messagebox !!!

--
Regards;
Mark Rosenkrantz
--
Spreadsheet Solutions
Uithoorn
Netherlands
--
E:
W: www.spreadsheetsolutions.nl
--

"headly" wrote in message
...
Is there a command to get the name of the running procedure?
The reason: My main procedure calls 10 smaller procedures; If any of those
10 procedures throws an error, i want to continue processing and i don't
only
want to capture the error code and description, but get the name of the
procedure where the error occured.