When you do an isdefined, CF is attempting a read of the variable name.
Yes. You do need a READ Lock around IsDefined Statements. I can't see why
a CFABORT inside of the CFLOCK would cause any kind of problem. I know
where your thought process is going... but I still sense no problem there.
Perhaps someone else has a more definitive answer about that aspect of your
question.
Patricia Lee
****************************************************
Cold Fusion Developer & Instructor, ACCD
Fig Leaf Software "We've Got you Covered"
****************************************************
[EMAIL PROTECTED] **** 202.797.5426 ****
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists