@apenhorwood wrote:
makes since because it is a quick use debugging tool. It is not meant to be left in the code past development. is not a debugging tool and should not have an abort attribute. I would say you should review your coding practices if you need to abort after a cfinclude.
Personally I think cfinclude is a bad practice in most cases, in that variables should never appear out of no where. The bad code I have seen over the last 15 years is mainly due to poor uses of cfinclude. Use a component and functions.
Andrew Penhorwood