http://livedocs.adobe.com/ Macromedia LiveDocs - online documentation with user feedback. Copyright 2009, Macromedia, Inc. 2009-11-25T01:03:31 en-us http://livedocs.adobe.com/coldfusion/7/htmldocs/00000242.htm#69808 What is interesting is that while CFERROR will not catch compile time errors like '<cfet x = 1 />', if you define a site wide error handler in CF Administrator, this error will get caught and the user will be redirected to your custom error template. The problem here is that this error template cannot be customized for a specific application, but will appear for all applications hosted on your stand alone server or JRun instance. Runrocket 0 0 2007-07-09T08:12:34 http://livedocs.adobe.com/coldfusion/7/htmldocs/00000242.htm#65306 What thekat is saying is that the CF template has to be compilable in order for errors that cferror can catch to occur. cferror is only for run time errors, doesn't work for compile time errors (which makes a lot of sense). DracTK 0 0 2007-04-12T09:11:44 http://livedocs.adobe.com/coldfusion/7/htmldocs/00000242.htm#50267 An additional note on CFError. Despite information above to the contrary, the cferror tag does not catch all CF errors, regardless of the TYPE attribute that you specify. For example, if you leave off the closing parenthesis in the following tag: #left(sometext, 20#, the CFError will NOT trigger. However, if you properly form the tag but pass an invalid variable (for example passing a misspelling of #left(smoetext, 20)#, the error template will trigger fine. For CFError to process, there can not be any malformed CF, just malformed variables, truncation, etc. thekat 0 0 2006-06-29T23:35:25