Thanks. I like the Fusebox approach. We may go that way for our next wave of building.
Chris Norloff
---------- Original Message ----------------------------------
From: "Christopher P. Maher" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Tue, 31 Oct 2000 15:11:47 -0500
>> Darn. So I can't even put them in with a couple CFINCLUDEs?
>>
>> thanks,
>> Chris Norloff
>
>There is a work around that will let you add a site wide CFTry/CFCatch in
>the application. Just do the following:
>
><CFTry>
> <CFInclude template="#cgi.script_name#">
><CFCatch>
>........
></CFCatch>
></CFTry>
>
><CFABORT>
>
>
>Essentially the application.cfm will run, include the script you wanted and
>then abort. Not pretty but it works in most configurations. You get into
>trouble if you have a lot of different paths.
>
>The better way to handle this would be to have everything run through some
>central template (as in the fusebox model). Then the error handling can be
>employed there. But if you already have your system running and have lots of
>different pages that are called directly, the application.cfm approach might
>be suitable.
>
>Chris
>
>---------------------------------------------------
>Christopher P. Maher
>mailto:[EMAIL PROTECTED]
>Maher Associates, Inc.
>Actuarial and Computer Consulting
>http://www.maherassociates.com
>
>
>
>
>------------------------------------------------------------------------------------------------
>Archives: http://www.mail-archive.com/[email protected]/
>Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
>with 'unsubscribe' in the body to [EMAIL PROTECTED]
>
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
