>No, to the best of my knowledge, the internal local scope of the custom tag
>isn't exposed to the calling page - after all, that would defeat the
>purpose
>of having a separate local scope, and anyway, the custom tag has finished
>executing (and its local scope no longer exists) by the time that you get
>back to the calling page in most cases.
>
>However, the problem that you're trying to solve can be approached another
>way, by simply passing to the custom tag the variable name that you want to
>create:
>
><cf_foo return="myvar">
>
>Then, within the custom tag, you can use the SetVariable function to create
>a variable in the calling page with the name "myvar":
>
><cfset valuetoreturn = "42">
><cfset rs = SetVariable("Caller." & Attributes.return, valuetoreturn)>
>
>In addition, you can use this syntax instead of SetVariable:
>
><cfset "Caller.#Attributes.return#" = valuetoreturn>
>
>While I prefer the SetVariable syntax for reasons I won't bother explaining
>now, either will work.
>
Thanks all. I didn't think you could do it, and your explanations make
sense. I'm going to go the SetVariable() to solve my problem.
Regards,
Dave.
______________________________________________________________________
This list and all House of Fusion resources hosted by CFHosting.com. The place for
dependable ColdFusion Hosting.
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
