> Seems to me if it generates an error which looks like a ColdFusion error then > we should be able to display something > other than that error. That is just a common security practice to NOT have > debug information go out to the public.
You can! This is why every application should include multiple levels of error handling. Exception handling using CFTRY and the onError event handler can only trap runtime exceptions. If the program in question can't even compile, they do not have any effect. The CFERROR tag can handle compiler errors using TYPE="REQUEST", but nobody uses that any more as a rule. The site-wide error handler can handle compiler errors and runtime exceptions. Of course, you should not have compiler errors on a production site - ever. If you do, this indicates that you have deployed code to production WITHOUT EVER TESTING IT AT ALL. But you should still use the site-wide error handler as a last level of defense against anything that can go wrong. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:353384 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
