Sorry.. I should have been more clear. The variable is not being accessed by any of the other pages; the variable "confirmed" is used solely by the page that is creating it. CFDUMP is a great troubleshooting tool, yes, if there are few iterations of a loop; if there is a lot of data, using CFDUMP in a loop of 3,500 iterations will slow processing down to a molasses crawl. Sometimes, this module will iterate 22,000 to 37,000 times, depending. IsDefined can prevent the module from breaking; but if the variable is not defined after a loop is done iterating - after it was defined at the beginning of the page (<cfset confirmed=0>) - then I am not sure what to do; I can't just arbitrarily throw a number into it, and the value that should be there is necessary to the process, not only for updating a log file, but also for displaying on the screen how many items were processed. The variable is not being deleted inside the loop; the last line inside the loop is <cfset confirmed = val(confirmed) + 1>; so it's there for every iteration. Somehow, after the loop is done and before <CFOUTPUT> displays it, it is removed. The loop is inside a CFTRY/CFCATCH, no errors are being displayed prior to the module breaking. So, I'm really scratching my head on this one. ^_^
... View more