Vista - Re: Err.Description does not contain the full text of the error me

The WSH message is a debugging message.
Err.Description is just that: the description
text of the specific error that was triggered.

Not to be insulting, but I think that should
be pretty obvious. You shouldn't have a
"variable is not defined" error once the script
is finished and in use. By the time you've
finished debugging you should generally know what
errors might happen and have them dealt with by
the script.
In other words, in the finished script you shouldn't
be getting unexpected errors. If you do then you
need to go back to debugging.

"mayayana" <mayaXXyana@xxxxxx> wrote in message
news:Of7DTpfGJHA.5028@xxxxxxYes, I prefer that my robust and well-debugged scripts encounter only those
errors that are expected. ;-)

/Al

My apologies for trying your patience.
Let me try again, more simply:

Errors have numbers and descriptive text.

Err.Description is that descriptive text.

The msgbox you see is the WSH debugger
showing you that descriptive text and telling
you the context.

If you post more detail about what problem you
actually need to solve then you might get a more
helpful answer.

> Yes, I prefer that my robust and well-debugged scripts encounter only
those Did you think my response was "highhanded"?
I can't think of any time I've ever dealt with Err.Description
outside of a debugging situation, except when I write
something like a class for use by others and want to
provide custom error feedback. But of course that's
also used in a debugging situation on their end. Once the
script is in use I might have something like:

If Err.Number <> 0 then....

But if I encounter an error that my script hasn't
prepared for then it's time for debugging again.
I was tryinng to point out that the description
isn't really applicable outside of debugging. No
one would do something like:

If Err.Description = "Object can't create object." then...

Even less likely would be:

If Instr(Err.Description, "Object can't create object") > 0 then
If Instr(Err.Description, "foo") > 0 then
MsgBox "Foo just fooed up.", 64, "Snazzy Script Feedback"
End If
End If

"mayayana" <mayaXXyana@xxxxxx> wrote in message
news:uZ1FvolGJHA.4560@xxxxxxNo. The expected/unexpected error thing is just one of my pet oxymorons...
;-)

/Al

<snip>