Could this have something to do with MX treating this somewhat differently in terms of case than earlier versions?
This is from a run down I saw recently about issues involved with upgrading to MX at: http://www.cfconf.org/cfun-02/talks/cfun02_migrating_from_cf5.ppt Form.FiledNames - returns Form.FieldNames in the order in which they were created and not in All Uppercase. Stephen > Also - I'd avoid using this variable for the sake of future > compatibility. It has the feel of something that might to be > depricated. Now that the FORM scope is a structure, the fieldnames > variable is redundant. Use StructKeyList( ). > > -Mark > > -----Original Message----- > From: Dave Watts [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 13, 2003 9:42 AM > To: CF-Talk > Subject: RE: Form.Fieldnames and MX > > > > Ok, what happened? I used to be able to loop through > > form.fieldnames to create a list of all of the fields > > and then I could write my processor script. CFMX, on > > the other hand, gives me the following: > > > > Element FIELDNAMES is undefined in FORM. > > This variable still exists in CFMX, whenever the page has received > an HTTP POST with data. So, you probably don't have a POST from your > HTML form. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > voice: (202) 797-5496 > fax: (202) 797-5444 > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
