I wondered why I couldn't trap it as well, but I don't semm to be able to...
when I step through, it initialzes the variables, but the returns the error.
Doesn't ever go into the page init.
I have thought about validation for this stuff, but I'm unsure as to how to
set the validation to only allow good characters. I would also like to
check to make sure that the title field is not all caps as well, but am at a
loss as to how to accomplish this.
Thanks,
Andrea
"Ken Cox [Microsoft MVP]" <BA************@sympatico.ca> wrote in message
news:e0*************@tk2msftngp13.phx.gbl...
Hi Andrea,
I'm curious why you can't trap that error. If you step through with the
debugger and use that input, it should tell you the nature of the error.
Then you can put it in a try...catch block.
Of course you can use validation to make sure the bad characters aren't
submitted.
"Andrea Williams" <an*******@hotmailIHateSpam.com> wrote in message
news:Oc**************@TK2MSFTNGP14.phx.gbl... I've created my own error handling object. and I wrtie tot eh error
handler
if the error is caught. Howver, I have one error it doesn't llok like I
can
catch.... In my form, if someone enters the < or > sign in a text box
field, I get a long ASP.Net error page... not pretty. So how do I
capture
that error and log it to my databae and give them a pretty error
message?
Andrea