Here are a couple of things to consider: - a catch will fail to work if the code in the catch causes an error itself, in which case the error will be passed up to the next higher errorhandler in the chain, or dumped to the screen like a traditional CF error. That said, I see your code shows your catch doing nothing that should fail to work, but then the comments above it suggest you’ve perhaps removed code you feel it sensitive or unimportant. Just know that if there’s any code that was in the real catch, you ay want to test if really removing it might make it work - but second, note that a cfcatch does not abort a request. You would need to do that, otherwise the code proceeds to the next line of code, which again in your case we can’t tell what’s next but I assume there was more code to this. You may want to see what happens if you add in an abort.
Let us know what you think or find. I realize it’s not “the solution” but it may help you get to it. /charlie From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of troy Sent: Wednesday, August 06, 2014 12:18 PM To: discussion@acfug.org Subject: RE: [ACFUG Discuss] Issue with cftry and Query of Queries <snip> But my real question is why the error escaped the try/catch block at all. <cfcatch type=”any”> should have caught anything regardless of whether the error originated in the contained logic block or some other method called by it, yes? Thank you, Troy Jones
