Correct me if I misunderstood what you are getting with your last example but from what I can tell the explanation below seems reasonable to me....
Because your last example doesn't even get compiled due to the closing > being missing on the cfoutput, CF doesn't see any code that you have in that template at all... Therefore the <cferror and the cftry block are not in memory to be fired... It's all about the timing of the error in the CF process. If its at compile time then there is very little you can do to stop the raw error... If it is a logic error in an otherwise valid template then the error handling you code will run. Paul ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:201951 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
