A runtime error, on
the other hand, is an error encountered while the script was being executed;
this is caused by errors that WSH doesn??™t know are errors until it actually
tries them, such as trying to read from a file that doesn??™t exist or trying to
calculate the square root of a negative number.
Lastly, the Description field shows a brief explanation of the error encountered.
Sometimes it??™s helpful, but most of the time it??™s either too vague or
too cryptic to be of much help. This is where programming experience
comes in handy for interpreting these messages and figuring out what
caused them. The following are a few of the more common error descriptions
and what they mean:
Expected ???)??™
Compilation error: you left out a closing parenthesis, such as at the end
of an InputBox statement. Note that sometimes you can have nested
parentheses (e.g., x=1+(6+7*(3-4))), and you need to make sure you
have an equal number of open and close parentheses.
Expected ???End??™
Compilation error: you left out a closing statement for a structure, such
as If, Sub, or For. Make sure you include End If, End Sub, and Next,
respectively. Note that WSH might report that the error occurred on
Figure 9-2. The Windows Script Host displays a message like this whenever it encounters
an error
542 | Chapter 9: Scripting and Automation
line 37 of a 35-line file; this happens because in looking for a closing
statement, WSH continues to search all the way to the end of the script,
at which time, if the statement was not found, it will report the error.
Pages:
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754