Vista - Error msg list or db. Newbie question.

Is there a database or list that tells you wath all the error messages mean
when running a vbscript?

I am trying to build a small script, but an error (0x80041021) occurs. I
haven't got a clue what that error means. There must be some documentation
that I can use in the futur, because I'm bound to make more errors.

When consulting the "Tales from the Script" pages about debugging (on the MS
TechNet) I found some clue, namely "Now look up error code 438 in the
VBScript documentation". Where does one find this information?

Kind regards.
Dramklukkel
-------
I fixed it right the first time.
It must have failed for other reasons.

I found this for your specific error:

http://www.computerperformance.co.uk...e_80041021.htm

I have at least a partial list of VBS errors from
VBScript Programmer's Reference (Wrox). They
all start with "800A". The first half or "high word"
is typically an indication of what type of error it is.
But the system seems to be poorly designed and
even worse on documentation. For instance, 800A
doesn't always mean script. IE also uses 800A.
And when I searched for 80041021, in 30 returns not
one link was from microsoft.com!

I find that if you want documentation for Microsoft
products then the best method by far is to ask Google.
Someone, somewhere has almost certainly already had
your problem and resolved it somewhere online.

I think that part of the reason for Microsoft's notable
disorderliness is that they want to sell everyone an
MSDN sunscription for several thousand dollars. The
less usable MSDN online is, the more likely that people
will find a need to buy a subscription to get their own
CDs.

(Have you noticed that microsoft.com pages seem to be
routinely moved without a forwarding link? It's almost
guaranteed that any microsoft.com link more than a
year or so old will go nowhere. One can only conclude that
either they don't want their docs found online or that
Microsoft simply doesn't know how to build a website.
.... I'm not sure which conclusion would be giving them
"the benefit of the doubt".

You can often get help here but you should post the
error code AND the description AND the code that caused
the error.
meandocumentationMS

So what it boils down to is, basicly I'm doomed when an error occurs. Well,
if I decide to rely on Microsoft that is.
That's what I needed to know. Thank you. :-)

Thank for the URL by the way.
And you're right about the website, but I've found no benefit for this doubt
so far. :-o

Greetings,
Ivo
--
I fixed it right the first time.
It must have failed for other reasons.


"mayayana" wrote: