processing. This is "wrong" by the way we want it to work - We would like the program to "quit" once an InvalidAccess has been encountered and InvalidAccess template has been set.
Yeah, me, too!
One solution we recognize is that the doBuildTemplate of the super screen simply throw InvalidAccessException and all the extended screens catch this exception and set the InvalidAccess template. But then this means that all the screens need to contains this catch block and exception handling that I would like to avoid.
Here's an idea. Throw InvalidAccessException and do NOT catch it in the subclassed screens. That should display the error template. In the error template, you could catch the InvalidAccessException and display your InvalidAccess template.
If this works, please tell me. I'd like to this as well.
Eric
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
