>Can you post the code for the set_first_name.cfm? Thanks for chiming in Byron. set_first_name.cfm is not a real file, but if it were, it would just look like this:
<cfset firstName = "Brian"> And it would work in all cases, except for the scenario that I'm describing (where the byte code is "incorrectly generated"). In that case, the <cfinclude> for set_first_name.cfm would not fail, but the firstName variable would never get set to "Brian", so any code later in the request lifecycle that expected the value to be "Brian" would not execute as expected. In other words, in the scenario I'm describing, none of the cfml code in the included file would ever be executed, unless we redeploy the exact same file, which will cause CF to regenerate the byte code (hopefully correctly this time) and fix the issue. I realize this may sound "unbelievable", so I am going to try to recreate this behavior on my local dev server and see if I can get my hands on the byte code in both the working state and the broken state. >From there, perhaps I'll be in a better position to provide you guys more >information to work with. I really appreciate everyone sharing their thoughts! Brian ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:359327 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
