I see, thank you for clarifying. I had wondered about the Variables
scope.
Then what is the advantage of explicitly putting them in the
Variables scope if they automatically go in anyway? Is it the speed
mentioned earlier? I'm only doing maybe 20 variables. And if I'm
still referencing
Alright! This works fine thanks.
I don't want do rewrite my variable scoping for this app, but I'll
consider having everything in Variables for the future as I write
this up as a general include.
It may be helpful to know/recall that all local variables live in a
scope structure called
Daniel Kessler wrote:
I don't want do rewrite my variable scoping for this app, but I'll
consider having everything in Variables for the future as I write
this up as a general include.
You wouldn't have to - his point is, every var called variablename is
also referenceable as
I have this code that goes through a db record set (with just one
record) and creates a structure, full of variables for referencing:
cfset db_info = StructNew()
cfloop list=#the_db.columnlist# index=col
cfset db_info[col] = the_db[col][currentRow]
!--- attempting to make
Can't you do it like
cfset #varname# = anothervar?
~|
Create robust enterprise, web RIAs.
Upgrade integrate Adobe Coldfusion MX7 with Flex 2
How about in your list loop:
cfset #col# = the_db[col][currentRow] and
cfset #col# =
-- Josh
- Original Message -
From: Scott Weikert [EMAIL PROTECTED]
To: CF-Talk cf-talk@houseoffusion.com
Sent: Monday, January 08, 2007 12:01 PM
Subject: Re: retrieve db into variables
Can't you
I'd rather it just create a variable with the field name and fill
it with content instead of sticking it in a structure.
It may be helpful to know/recall that all local variables live in a scope
structure called Variables. So you can just use that instead of the structure
you create yourself:
7 matches
Mail list logo