Did not know that was a keyword. I was browsing for some example
code and came across one that had a little of what I was looking for.

The err handler was part of that macro and I left it intact, and it
was useful to a degree as I puttered with the code

Well I'm sure VB[A] could easily figure out the procedure has a label
named "Err:", but it's just not good practice to use (or misuse)
built-in keywords that way. That's not much different than writing...

On Error GoTo Error
OR
On Error GoTo GoTo

...and should have been readily recognized as bad coding when you saw
the lines...

Err:
MsgBox Err.Description

...IMO!<g That's the problem with using 'found code' *as is* without
revising it to your own standards or coding conventions (if you even
have those in place yet)!<g

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion