On May 26, 2005, at 11:59 AM, Alex Brelsfoard wrote: > Yeah, but still we need to remember to put that hidden field in to > hold > the place of the checkbox's name. > Part of my problem is that there are MANY differen humans who are > making > forms who use my script. WAY too much human error availability. My > helper script that reads the HTML to create a list of fields is a bit > safer (though still not the answer I'm looking for). > <shrug> > --Alex >
So, many people are making forms with arbitrary field names. Hand coding? Is it unwise to expect these people to report the names of new fields, perhaps via yet another form...? A form creation GUI that also reports field names to the form processor is overkill, I suppose. Is there an HTML::LinkExtor for form inputs? There is also the question of why, how and whether your application needs to know the names of fields for which there is no value. Chris has hit on something. What if you had a flexible storage mechanism that was capable of essentially adding new columns to your database table as they arrived? If anyone answered yes, then everyone else automatically answered no. That is, unless the table was dedicated to a form that kept changing all the time and you were required to know who specifically declined to answer versus who never saw it... Bogart _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
