Why do you think you want to catch it in the webform? What do you expect to
do about such an exception? Are you concerned about some one particular
exception, or just exceptions in general?
Is your control explicitly throwing a particular exception? If so, then
please stop doing that. Exceptions are for exceptional circumstances.
They're not a general non-local goto.
You say it's not that easy with composite controls. You're dead wrong. Your
situation is in no way specific to controls, much less to composite
controls. This is nothing more than a chain of subroutine calls. I strongly
recommend that you stop asking your questions about controls and instead
just ask them about subroutines calling subroutines which call subroutines.
Has this exception ever occurred? In that case, one really big hint will be
the stack trace. Look at the trace and pretend you've never even _heard_
about controls!
If necessary, post the stack trace and I'll become less general. But I'm
concerned that if I do that, you won't learn the real lesson - that this has
nothing whatsoever to do with controls.
--
John Saunders
Internet Engineer
jo***********@s urfcontrol.com
"Kyle Johnson" <kl******@hotma il.com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
my problem is. Where do I catch the exception in the webform? If the was
a user control made of of html controls it would be simple but it's not
that easy with composite controls. I want to catch it at the webform
level
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!