There are at least two ways form fields can fail to be passed:
1) If you don't put METHOD="post" (I suppose METHOD="get" works too) in
your opening FORM tag, the form variables get passed in the URL instead
of the form. Goofy, huh?
2) Apparently there are certain reserved words you cannot use in your
fieldnames. I discovered quite by accident that a field like START_DATE
will not be passed because of the _DATE part of the fieldname. Not sure
why, I think it may have something to do with CF's data input validation
grabbing it first. Try renaming your fieldnames if the METHOD="POST"
doesn't work. Of course you know that you can't start a fieldname with
a numeric or odd character, right?
Regards,
Karl Simanonok
Advanta Solutions, Inc.
Original message:
============
Date: Tue, 11 Jul 2000 23:37:20 -0400
From: "Dave Watts" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Subject: RE: Form.Fieldnames Missing
Message-ID: <001001bfebb2$93c4af70$[EMAIL PROTECTED]>
> Is there a reason why the form.fieldnames field would not be
> passed in a form?
I vaguely seem to recall that in some versions of CF prior to 4.5.x, if
the
ENCTYPE attribute of the form is set to "multipart/form-data", which is
what
you'd use for file uploads, FORM.FIELDNAMES wouldn't appear.
Unfortunately,
I can't test that theory, since I'm running 4.5.1.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
