Thanks for the response. We tried to avoid explicitly adding CFTRY within individual file. Instead we want to have a site-wide error handler that only needs to be "called" from one place, such as application.cfm. Also, if your index.cfm uses CFLOCATION, then the target file will fall out of the CFTRY trap. Jie-hong > >Date: Mon, 9 Oct 2000 10:18:58 -0400 >From: "Stewart, Mark" <[EMAIL PROTECTED]> >To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> >Subject: RE: Can app_globals.cfm replace application.cfm and error handlin > g >Message-ID: <[EMAIL PROTECTED]> > >Just off the top of my balding head, I would say ditch the cferror stuff and >go strictly to cftry and cfcatch. If an error occurs, it's best to catch it >right then and there. In addition to that, you can place a cftry and cfcatch >around your index.cfm pages to catch anything that slipped through the >cracks. > >~Mark > ------------------------------------------------------------------------------ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
