What Isaac just said :-) I'd have to shut it off to find out for sure, but I'm pretty sure the REI setting, if off, also restricts the information that my error handler delivers. Isaac mentioned the stack trace and I believe this also includes error.tagcontext (but maybe not... again I'd have to try it to be sure). That struct nails down the error location precisely. Otherwise you'll get an error on line 5 of foo.cfm when in fact it was Line 5 of a custom tag, bar.cfm, which was called by foo.cfm.
I always have a site-wide error handler backing up my in-application error handling so nobody ever... ever sees a raw CF error onscreen. Thats the real message here: Always always use error handling. -- --mattRobertson-- Janitor, MSB Web Systems mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:207394 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
