Variable is undefined help

[x6213]

I get a "Variable is undefined" error but I have no idea which variable. I'm editing pre-existing code and there are numerous variables, so the only way I've been able to debug is to ' comment out each variable one by one and see if the error stops to find the faulty variable, but this is very time consuming.
Is there a way to make the error show which variable is undiffined? (such as an error sub
(btw, using vbscript and legacy asp )
thank

 

[DotNetGnat]

are you using

<%Option Explicit%> on the top of your page...

-DNG

 

[x6213]

yes, it's the first line of my global include

 

[DotNetGnat]

also put on the top of the page on which you are getting errors...

Turning on this option helps to identify undefined variables...

-DNG

 

[DotNetGnat]

the thing is that you should receive error which looks something like this:

Variable is undefined: varname

but as per your post i dont think you are seeing this kind of error...

what is the actual error that you are getting...

-DNG

 

[x6213]

this is what shows

Technical Information (for support personnel)
Variable is undefined


but no varname

 

[DotNetGnat]

can you post the code here or is it very big to post...also if you atleast post the suspicious parts of your code..that will do...

-DNG

 

[DotNetGnat]

and i think that you are using a custom error page...turn that off for a moment to see the actual error...

-DNG

 

[Sheco]

Does it say anything after Variable is undefined?

Did you turn off the "show friendly errors" option?

 

[DotNetGnat]

Sheco,

By looking at the error he posted, dont you think it is a custom error page??

-DNG

 

[Sheco]

Could be but also the default friendly error has the same or similar wording.. something about "for support personnel"

 

[x6213]

the actual Err.Description is just "Variable is undefined

 

[DotNetGnat]

may be Err.Number or Err.Source might give any additional help...but go ahead and uncheck show friendly HTTP error messages in the Internet Tools ->options...

-DNG

 

[x6213]

ok, i feel stupid. It was a "On Error Resume Next" set in one of the includes. Now I get a line number of the error, thanks for all your help everyone.

 

[Sheco]

Don't feel stupid, that kind of thing happens to everyone.

 

[DotNetGnat]

I agree...only these kind of little things always are the diffcult and most time consuming one...

-DNG