No problem at all. Glad to help.

Here's my Errors database, which contains the proc and table. This is my standard, BTW. I don't like doing error logging or the like in the primary database because a rogue process could cause the database or the disk to fill up. This database has a max size, so it won't crash anything if it fills up. You'll notice I also have a standard proc template which includes a call to that errors proc. So far, it's worked really well.