>So with CFTransaction, the only reason to use <CFTRY> is if you want >additional error handling? For example, if I want details every time this >fails, I could use try within a transaction to capture failure reason? Is >there a better way? > >Do you normally attempt to capture the reason that a transaction fails?
I wouldn't use <cftry> around each individual query in the <cftransaction> to begin with. The reason why you are using the <cftransaction> tag to begin with is because you want your logic to be executed as one block of code whereby if one query fails, within that block, everything gets rolled back. I, instead, would put a <cftry> block around the <cftransaction> tags if you want this granular error-handling, and in my <cfcatch> block, I would use the "cfcatch" scope (i.e., cfcatch.message, cfcatch.detail, etc.) to output the specific diagnostic information to pin down where in your <cftransaction> the code failed. For more information on the "cfcatch" scope, see the documentation: <http://livedocs.macromedia.com/cfmxdocs/CFML_Reference/Tags-pt318.jsp#1104557> Regards, Dave. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
