Re: REPOST

I found this odd as well, since it's HTML code that's been around. I have a 
theory why some, including myself, are using checkboxes with the same name 
attribute to get a list with commas, while others are having to give 
different names to get the same result. It's not the HTML, but the 
processing of what the form sends. The form sends the values separated by 
&, but it's up to the called form handler to format it. I use XHTML with 
the same name on things I want grouped, calling a cgi script. Have done 
this for years. It, and past scripts, have stuck same named checkboxes 
together always. There must be something about the function cbirds is using 
that does not do this.

In short, the HTML form sends the values. It cares not how they are 
displayed on the other side, that's not its job. That's my guess anyway, 
since it's work for me with the same name. And I know it's just academic, 
since cbirds seems to have resolved his problem anyway. Just had to comment.

- Greg Hart

At 04:35 PM 2/18/03 -0700, you wrote:
>Klaas De Waele wrote:
>>>Nope, as I discovered before the suggestion was made, unlike radio 
>>>buttons which only allow you to choose ONE, I had to give them unique 
>>>names, such as volunteer1, volunteer2, volunteer3, etc.... and then it works...
>>
>>Strange, because I really really am using that comma seperated thingy in my
>>code.
>>Here's a demo:
>>http://www.grace.be/tests/form
>>
>>- Kayjey -
>>www.fiatcoupe.net
>
>Ahh, yes... and let us look at that code.
>
>You are using an "ID" deliminter and -- probably -- ASP code to spit out 
>results based on the "ID" rather than the "name". I don't work with ASP so 
>I'm guessing here.
>
>
>Website Rob
>Sitemaster at
>http://www.PotentProducts.com/
>------------------------------------------
>Helping people Host and Create their Web Site

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA