> what you are describing is not possible (as far as I know). I know it may
> *seem* like that's what's happening, but something else is going on
here...
See, I'm saying the same thing to myself too, but this code is so
"black-and-white" (seemingly), that there's nothing that stands out. Here is
the code I'm using, line for line, up to the CFLOCATION call:
<!--- If the user has clicked the Next button or asked to re-calculate
their selected values, update appropriate nodes with the form data --->
<cfif IsDefined("form.next") OR (IsDefined("form.recalculate") AND
form.recalculate)>
<!--- Update appropriate nodes with the form data --->
<cfscript>
// Update the asking rent values. USE is the radio button value and
USER is the user-defined value.
variables.sourceData.market.rent["USE"] = form.askingRent;
variables.sourceData.market.rent["USER"] = Val(form.askingRentMyValue);
// Update the rent discount values. USE is the radio button value and USER
is the user-defined value.
variables.sourceData.market.rentdiscount["USE"] = form.rentDiscount;
variables.sourceData.market.rentdiscount["USER"] =
Val(form.rentDiscountMyValue);
</cfscript>
<!--- This include file is literally one line: a CFWDDX serialization --->
<cfinclude template="act_serializeSourceDataNode.cfm">
<!--- Re-direct the user only if they have clicked the Next button -- not if
they have asked to recalculate their selected values --->
<cfif IsDefined("form.next")>
<!--- Send the user to the next page --->
<cflocation url="dsp_ContractRentSelForecast.cfm?reportid=#form.reportid#"
addToken="no">
<cfelse>
<!--- Re-serialize the updated CF structure so that the custom tag can be
called again outside of the CFIF logic --->
<cfwddx action="CFML2WDDX" input="#variables.sourceData#"
output="variables.sourceDataWDDX">
</cfif>
</cfif>
<cf_customtag>
That's it. That's all that's happening. I know the wraps the e-mail has put
on the code has probably made it all garbled, but if you cut and paste the
code into Studio, it should make sense.
>
> Perhaps one of these is happening...
>
> 1. the custom tag may be called somewhere else as well and you don't
> realize it...
Don't see it if it is.
> 2. the cflocate is somehow taking you back to the same page, but the
second
> time around the form variables don't exist...
The page this code is on is called dsp_ContractRentCurrent.cfm, which is
obviously a different name than the CFLOCATION tag is calling.
> 3. you have an OnRequestEnd.cfm file executing the custom tag
No. Not using one.
> 4. you're inadvertantly mixing up two files of the same name. I do this
> sometimes when I have multiple versions of a file in different
directories.
>
> who knows... could be anything. Good luck :)
>
Nah, not that either. I use version control, so this directory only has the
latest and greatest!
Thanks so much for your feedback. They were good points to look into.
Any other ideas?
Dave.
______________________________________________________________________
Signup for the Fusion Authority news alert and keep up with the latest news in
ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
