Hi,

Take all the time you need! It's a good thing you're going to test it first in the field. The code will benefit from that.

For me personally the only errors I'm trully interested in are the ones I didn't anticipate!

That means that my select case will handle all of those foreseen and my error logging gets the ones I didn't. More important including the source in the stack and the Error line (Erl())

That would be sufficient. But like I said before if you want something to help you debugging from a distance the errorhandler couldn't be big enough.

Don't forget if you design your error handling wel you could also use a separate DLL to process the Error log. This could be slimmed down for a release version but if need be you could easily replace that with a bulkier one!

But the Error lines have to be in the code to begin with otherwise that trick won't work...

So yes I'm very interested in the way this global thingie is growing...

So for now I hope I've given you again some more water to grow!