Developer Extraordinaire
-Original Message-
From: Paul Giesenhagen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 4:54 PM
To: CF-Talk
Subject: Re: Form.FIELDNAME - error
I understand your point, but it is like saying periods clutter up pages in a
book.
If you have:
cfset
I wouldn't call that bad practice, It should actually be
called good practice (at least in my book). You are setting
a variable and the ## around the variable show that it is
a variable, makes for easier reading. Now, ## on the set
side would be considered bad practice.
The use of pound
The speed issue? About the same difference as cfif vs.
cfswitch...
The main reason I would use switch over if is to make it
easer to read, and easier to maintain. That it is faster
is just a bonus.
This implies that CFSWITCH is always easier to read and maintain, and always
faster.
If the page was called directly and not from a form submission you could get
that error because no FORM fields are defined.
Reuben Poon
-Original Message-
From: Chakka, Sudheer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 1:16 PM
To: CF-Talk
Subject: Form.FIELDNAME -
make sure you're in a cfoutput...
v/r,
Jeff
-Original Message-
From: Chakka, Sudheer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 4:16 PM
To: CF-Talk
Subject: Form.FIELDNAME - error
Hi,
Can any one tell me what is the mistake in
CFLOOP FROM=1
i take that back, that shouldn't matter.
-Original Message-
From: Jeff Brown [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 4:27 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
make sure you're in a cfoutput...
v/r,
Jeff
-Original Message-
From: Chakka
Not sure if this is an error or just a bad practice, but you don't need the
# signs in your variable declaration (cfset)
CFSET var = ListGetAt(Form.FIELDNAMES, i)
works just fine. Also you don't need to generate that var at all you can
just do a list loop like this:
CFLOOP
Hi Reuben,
I am submitting using Post method. I am using FuseBox3. Will that make
a difference??
Thanks,
Sudheer Chakka
-Original Message-
From: Reuben Poon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 3:24 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
Tim,
I wouldn't call that bad practice, It should actually be called good
practice (at least in my book). You are setting a variable and the ##
around the variable show that it is a variable, makes for easier reading.
Now, ## on the set side would be considered bad practice.
my .02
Paul
, May 09, 2002 4:28 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
Not sure if this is an error or just a bad practice, but you
don't need the
# signs in your variable declaration (cfset)
CFSET var = ListGetAt(Form.FIELDNAMES, i)
works just fine. Also you don't need to generate
, Sudheer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 1:28 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
Importance: Low
Hi Reuben,
I am submitting using Post method. I am using FuseBox3. Will that make
a difference??
Thanks,
Sudheer Chakka
-Original Message-
From
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 3:28 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
Not sure if this is an error or just a bad practice, but you don't need the
# signs in your variable declaration (cfset)
CFSET var = ListGetAt(Form.FIELDNAMES, i)
works just fine
all url and form variables into the attributes scope.
Tim Heald
ACP/CCFD :)
Application Development
www.schoollink.net
-Original Message-
From: Chakka, Sudheer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 4:28 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
Hi
my_var = another_var
So my .02 is that pounds just clutter up your statement.
Reuben Poon
-Original Message-
From: Paul Giesenhagen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 1:35 PM
To: CF-Talk
Subject: Re: Form.FIELDNAME - error
Importance: Low
Tim,
I wouldn't call
my_var = another_var
So my .02 is that pounds just clutter up your statement.
Reuben Poon
-Original Message-
From: Paul Giesenhagen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 1:35 PM
To: CF-Talk
Subject: Re: Form.FIELDNAME - error
Importance: Low
Tim,
I wouldn't
: Re: Form.FIELDNAME - error
Importance: Low
I understand your point, but it is like saying periods clutter up pages in a
book.
If you have:
cfset variables.my_var = #query.column#
That tells me that there is a variable being set and it is a string
cfset variables.my_var = query.column
Am
Nope all discussion is encouraged!!! Unless it gets ugly
Douglas Brown
Email: [EMAIL PROTECTED]
- Original Message -
From: Reuben Poon [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Thursday, May 09, 2002 2:10 PM
Subject: RE: Form.FIELDNAME - error
I'd like to continue
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 5:10 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
I'd like to continue this but I am relatively new to this forum.
Are these types of debates encouraged/discouraged? Should they be taken
offline?
Reuben Poon
-Talk
Subject: Re: Form.FIELDNAME - error
I understand your point, but it is like saying periods clutter up pages
in a
book.
If you have:
cfset variables.my_var = #query.column#
That tells me that there is a variable being set and it is a string
cfset variables.my_var = query.column
Am I
to this forum.
Are these types of debates encouraged/discouraged? Should they be taken
offline?
Reuben Poon
-Original Message-
From: Paul Giesenhagen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 1:54 PM
To: CF-Talk
Subject: Re: Form.FIELDNAME - error
Importance: Low
.
Reuben Poon
-Original Message-
From: Paul Giesenhagen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 1:35 PM
To: CF-Talk
Subject: Re: Form.FIELDNAME - error
Importance: Low
Tim,
I wouldn't call that bad practice, It should actually be called good
practice
suggestions.
Thanks,
Sudheer Chakka.
-Original Message-
From: Reuben Poon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 3:44 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
I think that the # on the right side of the set operand is redundant.
CFSET my_var = #another_var
participated in this
discussion.
Sudheer Chakka.
-Original Message-
From: Timothy Heald [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 4:15 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
I think as long as it has something to do with CF and you don't let your
emotions carry
:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 5:20 PM
To: CF-Talk
Subject: Re: Form.FIELDNAME - error
:) they are common ... they get discouraged when the go on and on ...but
usually this group is very informative and you can learn alot by the
debates!
Paul Giesenhagen
QuillDesign
:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 4:25 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
Have we found out what the source of the original error is yet? I love a
good debate, but I would really like to help out the person who started this
thread as well.
Tim Heald
ACP/CCFD
The cache monster strikes again :)
Tim Heald
ACP/CCFD :)
Application Development
www.schoollink.net
-Original Message-
From: Chakka, Sudheer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 5:18 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
Well Guys,
I am
Chakka.
-Original Message-
From: Timothy Heald [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 4:31 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
The cache monster strikes again :)
Tim Heald
ACP/CCFD :)
Application Development
www.schoollink.net
-Original Message
cfset variables.my_var = query.column
Am I setting my variable to the two words seperated by a period,
query.column? or to a variable query.column?
The first. If you wanted to set myVar to a variable query.column, don't use
quotes. (Either way, the period should be a _ or some such.)
SO,
MyQuery.RecordCount and I think this is
easier to read (for me anyway) than cfif MyQuery.RecordCount GT 0.
Matt
- Original Message -
From: Paul Giesenhagen [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Friday, May 10, 2002 8:53 AM
Subject: Re: Form.FIELDNAME - error
I understand your
Sudheer,
For future reference. The caching problem created an error probably because
the FORM variables were not defined.
Reuben
-Original Message-
From: Chakka, Sudheer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 2:25 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
: Matthew Walker [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 5:03 PM
To: CF-Talk
Subject: Re: Form.FIELDNAME - error
I vote for Reuben on this. I disagree with your argument. While you want
periods in a book. You. Don't. Want. Too. Many. Of. Them. People new to CF
often over use
Hi,
That didn't solve my problem. It is not even recognising the
Form.FieldNames
CFLOOP list=#form.fieldnames# index=formField
#formField# = #evaluate('form' formField)# br /
/CFLOOP
it is giving error in the first line of the above code.
Any more
to read (for me anyway) than cfif MyQuery.RecordCount GT 0.
Matt
- Original Message -
From: Paul Giesenhagen [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Friday, May 10, 2002 8:53 AM
Subject: Re: Form.FIELDNAME - error
I understand your point, but it is like saying
Very cool. That's going in the snippets.
Tim Heald
ACP/CCFD :)
Application Development
www.schoollink.net
-Original Message-
From: Andrew Tyrone [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 5:41 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
Hi
think it is good to just educate the new CF users.
Reuben
-Original Message-
From: Paul Giesenhagen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 2:48 PM
To: CF-Talk
Subject: Re: Form.FIELDNAME - error
Importance: Low
I guess my example was:
cfquery datasource=dsn name
to most rdbms.
Tim Heald
ACP/CCFD :)
Application Development
www.schoollink.net
-Original Message-
From: Paul Giesenhagen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 5:48 PM
To: CF-Talk
Subject: Re: Form.FIELDNAME - error
I guess my example was:
cfquery datasource
.
Reuben
-Original Message-
From: Paul Giesenhagen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 2:48 PM
To: CF-Talk
Subject: Re: Form.FIELDNAME - error
Importance: Low
I guess my example was:
cfquery datasource=dsn name=getitems
select first_name, last_name
Cool. I'm not that nitpicky about something this inconsequential. But it
was a good conversation. Thanks guys!
Reuben Poon
-Original Message-
From: Paul Giesenhagen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 3:03 PM
To: CF-Talk
Subject: Re: Form.FIELDNAME - error
and assist the
beginner to the standard.
My 0.02
Tim Heald
ACP/CCFD :)
Application Development
www.schoollink.net
-Original Message-
From: Timothy Heald [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 5:56 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
I would think
-Original Message-
From: Timothy Heald [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 09, 2002 5:56 PM
To: CF-Talk
Subject: RE: Form.FIELDNAME - error
I would think that best practices in this case would be to allow the DB
to
do it's job. I know on SQL Server I do
40 matches
Mail list logo
