Hi:

In the "old" ASP (I think pre V5) if my page had an error, it would try to 
write the page and then show an error when it came to it.

I liked this because I could pretty easily find out what data variables 
held which helped me debug the problem.

In ASP.NET if there's an error, the page doesn't even think about 
rendering.

My question: I've got a variable: strSQL which I'm sure is the culprit and 
I could fix it in seconds if I could just see what it is.

Any ideas? (I suppose I should go to C# debugging 101?)

Duh! Sorry guys, that was too easy. The Debugger actually lets me set 
break points and use the Immediate window (imagine that)!

> Hi:

> In the "old" ASP (I think pre V5) if my page had an error, it would try 
to 
w> rite the page and then show an error when it came to it.

> I liked this because I could pretty easily find out what data variables 
h> eld which helped me debug the problem.

> In ASP.NET if there's an error, the page doesn't even think about 
r> endering.

> My question: I've got a variable: strSQL which I'm sure is the culprit 
and 
I>  could fix it in seconds if I could just see what it is.

> Any ideas? (I suppose I should go to C# debugging 101?)