I won't wander too far, but it might be a while before I kick out something with which I'm satisfied. The benefit of the delay to VBAX KB users will be that it'll be incorporated shortly into various projects serving several hundreds of people, so the major kinks should be worked out prior to submission.

In the meantime, I've added err.source. For some reason I had thought that err.source always returned the name of the application, but I see now that I was mistaken. At any rate, I'm not sure that it adds anything at this point, since I push the call stack with ProjectName.ModuleName.ProcedureName before there is an error, and err.source is obviously only available after an error has arisen. I suppose I could send the err.source as a parameter to the global error handler, but I don't see any advantage to that method over what I'm currently using. Perhaps you have some thoughts on that matter.

I've also included a loop to enumerate everything in the environment table.