dhodgdon
Posts: 80
|
| Posted: 04/25/2005, 8:45 AM |
|
Creating a Checkbox List associated with a database column and using a List of Values from the Forms Toolbox performs as promised except that I was under the impression it would only allow a single box to be checked in the form.
I get a warning when I generate code:
Warning: Record Users1 -> CheckBoxList BOGroup : For the CheckBox List only the first value is inserted or updated.
And, as warned, the first box checked, when multiple boxes are checked, is the one stored, but this is of little use when trying to make the form idiot proof. Is there some way to make the Checkbox List mutually exclusive at the form level, not just when the form is submitted? I prefer the multi-check box approach for this field versus the list box.
_________________
Regards,
David Hodgdon
|
 |
 |
peterr
Posts: 5971
|
| Posted: 04/25/2005, 11:36 AM |
|
The purpose of checkbox-list is to allow multiple selections. The purpose of radio-list is to allow single selection, so please use radio-list. This is standard used everywhere.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
dhodgdon
Posts: 80
|
| Posted: 04/25/2005, 1:15 PM |
|
Thanks for the reply Peter but your response is contrary to both the behavior of the control and the CCS help documentation.
From the CCS Checkbox List Overview Help page:
"A Checkbox List is very much like a Listbox which contains multiple options for the user to select from. If a Checkbox List control is associated with a database column or database expression, the user can select only one value to be inserted or updated into the database."
My control is associated with a column and though multiple boxes can be checked (which I don't want), only the "first" checked value is entered into the database which validates the warning I received at build time:
Warning: Record Users1 -> CheckBoxList BOGroup : For the CheckBox List only the first value is inserted or updated.
If the Checkbox list generated by the Toolbox allowed multiple selections, then it would be nothing like a List Box. Also, there would be no need for the warning when the page is generated. To me it begs the question, why have it in the Toolbox? And why is the Radio Button not called Radio Button List since that is exactly what it is?
I don't mean to be argumentative here, but I know what the documentation is saying and what the behavior of the program is. I have no passion for a check box, a radio list would be fine too. I built a radio button list and it works so I am sticking with it. HOWEVER, CCS needs to have its Checkbox List Overview Help page changed to reflect the purpose and behavior of a Checkbox list or make the Checkbox list behavior consistent with the help description.
_________________
Regards,
David Hodgdon
|
|
|
|
peterr
Posts: 5971
|
| Posted: 04/25/2005, 2:04 PM |
|
List Box can also allow multiple selections and can work identically to Checbox list. The analogy can be understood or misunderstood 
The checkbox list is in the toolbox because our users asked for it, even though for technical reasons we couldn't yet make it work the way everyone might want (there are several possible ways). I'm not sure how we can handle conflicting requests, but I'd agree with others to better have something than nothing.
Finally, when I design a Website I don't think about comparing listbox to checkbox but about what I need. Radio List is commonly accepted standard and available in HTML specs specifically for such purposes as you mentioned.
As for component naming, it's not my area and I am not sure why Radio Button is not called Radio Button List. Possibly because it's dual (could be single or multiple), while single Chekbox works differently from Checkbox list.
Hope this helps.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
|
