Debugging ASP Script

Now you've done your best to waterproof your code, but errors always manage to seep through. So how doyou go about removing the little blighters? One difficulty you might encounterwhen debugging is finding out exactly where the error is occurring. Rememberthe first ASP error we showed you? We tried to access the Document object from within ASP:

Microsoft VBScript runtime error '800a01a8'

Object required: 'Document'

/BegAsp/Debug.asp, line 5

That's pretty easy to follow, but we've already mentionedthat not all errors generate messages. Even if your error does generate amessage, it is not always the line that is at fault that generates the errormessage (as in a type mismatch error).  Let's look atsome tips you can use to make your errors easier to find.