http://livedocs.adobe.com/ Macromedia LiveDocs - online documentation with user feedback. Copyright 2009, Macromedia, Inc. 2009-11-25T02:07:48 en-us http://livedocs.adobe.com/coldfusion/6/CFML_Reference/Tags-pt315.htm#15108 This is not a very good example of how to emply CFTRANSACTION, it does not show how to use the various actions.. Its pretty much a shot in the dark unless you get the livedocs for CF5 (which is more detailed) but following the code there is invalid because cftry requires the last tag executed within itself be cfcatch.. so the method of catching and setting a variable in that method doesn't work.. This is how you need to do it..<br /><br /><Cfset gotrue=1><br /><cftransaction><br /> <cftry>...queries here...<br /> <cfcatch>...catch the error...<br /> <cfset gotrue=0><br /> <cftransaction action="rollback"><br /> <cfrethrow> <!---This line throws the error back to your error handler if you have one.. If you don't, you can remove this...---><br /> </cfcatch><br /> </cftry><br /> <cfif gotrue eq 1><br /> ...do something...<br /> <cftransaction action="commit"><br /> </cfif><br /></cftransaction><br /><br />Livedocs really needs to improve this page, very badly... ThisIsMe 0 0 2004-05-20T09:06:46 http://livedocs.adobe.com/coldfusion/6/CFML_Reference/Tags-pt315.htm#4420 CFTRANSACTION and TRANSACTIONs created in SQL Server stored procedures should only be used to encapsulate code performing UPDATEs, INSERTs and DELETEs. This means that any SELECT statements should be outside of your TRANSACTIONs to avoid locking rows unnecessarily. If your stored procs are called from within a CFTRANSACTION, you should avoid unnecessary SELECTs or move the encapsulation into your SQL Server Stored Procedure and hence move the business logic. <br /><br />The consequence of failing to do this is slower code since it is waiting for row and table locks to be released under small load. It can also lead to blocking on your server. earnshavian 0 0 2003-12-10T07:50:50