Which of these is best?
1.
cfset x = getValues[colname][rownum]
CFINPUT Name=#x# value=#DefaultValue#
2.
cfset x = #x#+1
CFINPUT Name=#getValues.ColName##x# value=#DefaultValue#
3.
CFINPUT Name=#getValues[colname][rownum]# value=#DefaultValue#
Considering that (1) and (3) will do
cfset x = getValues[colname][rownum]
This'll work with Access?
Since it's referring to a recordset, or Query object, in CF, the source of
that Query object is irrelevant. Yes, it'll work with Access, in that sense.
I've been reading that evaluate is a bad idea, but
I'm still not clear
post more of your code please
Ade
-Original Message-
From: Thane Sherrington [mailto:[EMAIL PROTECTED]]
Sent: 26 April 2002 17:12
To: CF-Talk
Subject: Variable names in CFINPUT
When using CFINPUT, is it possible to do something like this?
CFINPUT Name=#VariableName#
Can we see the template that's producing the error?
Tim Heald
ACP/CCFD :)
Application Development
www.schoollink.net
-Original Message-
From: Thane Sherrington [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 26, 2002 12:12 PM
To: CF-Talk
Subject: Variable names in CFINPUT
When
: Variable names in CFINPUT
post more of your code please
Ade
-Original Message-
From: Thane Sherrington [mailto:[EMAIL PROTECTED]]
Sent: 26 April 2002 17:12
To: CF-Talk
Subject: Variable names in CFINPUT
When using CFINPUT, is it possible to do something like this?
CFINPUT Name=#VariableName
At 05:16 PM 4/26/02 +0100, Adrian Lynch wrote:
post more of your code please
I'll have to get it from home. Basically, I have a set of variable names
and values that I get from a query.
So it's something like this:
CFQUERY name=GetFields datasource=#dsn#
SELECT FieldName
take it out of the cfinput and see what it's producing
-Original Message-
From: Thane Sherrington [mailto:[EMAIL PROTECTED]]
Sent: 26 April 2002 17:33
To: CF-Talk
Subject: RE: Variable names in CFINPUT
At 05:16 PM 4/26/02 +0100, Adrian Lynch wrote:
post more of your code please
I'll
To: CF-Talk
Subject: RE: Variable names in CFINPUT
take it out of the cfinput and see what it's producing
-Original Message-
From: Thane Sherrington [mailto:[EMAIL PROTECTED]]
Sent: 26 April 2002 17:33
To: CF-Talk
Subject: RE: Variable names in CFINPUT
At 05:16 PM 4/26/02 +0100, Adrian
]]
Sent: Friday, April 26, 2002 12:47 PM
To: CF-Talk
Subject: RE: Variable names in CFINPUT
take it out of the cfinput and see what it's producing
-Original Message-
From: Thane Sherrington [mailto:[EMAIL PROTECTED]]
Sent: 26 April 2002 17:33
To: CF-Talk
Subject: RE: Variable names in CFINPUT
Add a counter
cfset i = 0
CFLOOP Query=GetFields
cfset i = #1#+1
CFQUERY name=GetValues datasource=#dsn#
SELECT #GetFields.FieldName#
FROM #TableName#
WHERE ID=#ID#
/CFQUERY
CFSET
-
From: Raymond Camden [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 26, 2002 2:12 PM
To: CF-Talk
Subject: RE: Variable names in CFINPUT
Add a counter
cfset i = 0
CFLOOP Query=GetFields
cfset i = #1#+1
CFQUERY name=GetValues datasource=#dsn#
SELECT
cfset x = getValues[colname][rownum]
CFINPUT Name=#x# value=#DefaultValue#
Help me out. I don't get it.
Why isn't this an evaluative action?
In the strictest sense, it is - you're evaluating a variable to get a value.
However, what Ray is referring to is the use of the Evaluate function,
At 02:11 PM 4/26/02 -0400, Raymond Camden wrote:
cfset x = getValues[colname][rownum]
This'll work with Access? I've been reading that evaluate is a bad idea,
but I'm still not clear on what to do instead - if you could explain it, or
suggest a webpage, it'd be great.
T
Thanks
David DiPietro
Systems Developer / Engineer
OSU College of Medicine Public Health
Voice (614) 292-5960
Fax (614) 292-0745
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 26, 2002 2:45 PM
To: CF-Talk
Subject: RE: Variable names in CFINPUT
College of Medicine Public Health
Voice (614) 292-5960
Fax (614) 292-0745
-Original Message-
From: David DiPietro [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 26, 2002 3:29 PM
To: CF-Talk
Subject: RE: Variable names in CFINPUT
Thanks
David DiPietro
Systems Developer / Engineer
OSU
15 matches
Mail list logo