D
dbuchanan
I am designing a table to contain a field to stores a value that must
indicate none, one, or many choices. The form will have a group box
with checkboxes (multi-choice)
You see the records in this table contain partially pre-configured
records. The records serve as "master" data that will later be inserted
into a data table. The master data is set up by an adminsitrator. The
administrator indicates for each record the none, one or many options
that apply to the record.
At that later time a user will want to add pre-configured records to
his/her data table. Based on the kind of project he/she will make a
selection in a group box of none, one, or many options. Then based on
that choic he/she will be presented with a filtered table displaying
the choices of pre-configured records to choose from.
Here is sample enumeration of the data that might be used as the
options to choose from.
Kitchen 1
Bathroom 2
Bedroom 4
Utility room 8
Garage 16
I know there are other approaches to achieving this, but this approach
seems the simplest. Among the reasons I think I favor this approach is
that it is not so "schema intensive".
Are there any reasons not to use this approach?
I intend to use a group box containing a list of checkboxes. When the
user makes his selection the the form adds together the values for the
selected choices to arrive at the value to store in the record.
I know there is nothing original about this approach, but I have
questions...
· What is the 1,2,4,8,16 kind of enumeration called. I hash table?
· How do I parse individual values from the sum so that I can
appropriately check or uncheck the checkboxes for the field?
And any recommendations?
indicate none, one, or many choices. The form will have a group box
with checkboxes (multi-choice)
You see the records in this table contain partially pre-configured
records. The records serve as "master" data that will later be inserted
into a data table. The master data is set up by an adminsitrator. The
administrator indicates for each record the none, one or many options
that apply to the record.
At that later time a user will want to add pre-configured records to
his/her data table. Based on the kind of project he/she will make a
selection in a group box of none, one, or many options. Then based on
that choic he/she will be presented with a filtered table displaying
the choices of pre-configured records to choose from.
Here is sample enumeration of the data that might be used as the
options to choose from.
Kitchen 1
Bathroom 2
Bedroom 4
Utility room 8
Garage 16
I know there are other approaches to achieving this, but this approach
seems the simplest. Among the reasons I think I favor this approach is
that it is not so "schema intensive".
Are there any reasons not to use this approach?
I intend to use a group box containing a list of checkboxes. When the
user makes his selection the the form adds together the values for the
selected choices to arrive at the value to store in the record.
I know there is nothing original about this approach, but I have
questions...
· What is the 1,2,4,8,16 kind of enumeration called. I hash table?
· How do I parse individual values from the sum so that I can
appropriately check or uncheck the checkboxes for the field?
And any recommendations?