OPTIONS GROUP

  • Thread starter Thread starter Elise R via AccessMonster.com
  • Start date Start date
E

Elise R via AccessMonster.com

I have a database in which I keep track of symptoms. I currently have nine
reactions within my Symptom Option Group. My problem is I can only choose
one symptom. Is it possible to choose more than one option from a group of
nine?
 
No, that is the whole point of an option group. One option can be selected.

You should instead use checkboxes bound to fields.
 
Thanks for your reply.

I turned the symptoms into checkboxes; however, I am still only allowed to
check one checkbox.

Please advise.
 
You can't just turn them into checkboxes.

An option box stores ONE value in ONE field.

You will need to add eight more fields. Each one named a symptom.


BUT, that is technically poor database design. Instead, you should have a
brand new separate table called SYMPTOMS where you create a separate record
for each symptom and a number to identify that symptom.

You add a third table called PATIENTSYMPTOMS or similar that has only your
patient number and symptom number.

Then, if a patient has two symptoms, they get two records added to that new
table. If they have 5 symptoms, they end up with five records.

This is called a many-to-many relationship.
 
You're right Rick, I created the checkboxes. I now have three tables.

tblReaction
LogNum
ReactionDate
Where (3 options)
Type (2 options)
When (3 options)
Symptoms (I listed nine separate symptoms)
Comments

tblSymptoms
Created as you suggested

tblPatientsSymptoms
Created as you suggested

If I change an options in one record, the option gets changed in all the
records. Also, the Where, Type & When and Comments are not being updated in
the table. Surely, I'm missing something that's very simple...


Rick said:
You can't just turn them into checkboxes.

An option box stores ONE value in ONE field.

You will need to add eight more fields. Each one named a symptom.

BUT, that is technically poor database design. Instead, you should have a
brand new separate table called SYMPTOMS where you create a separate record
for each symptom and a number to identify that symptom.

You add a third table called PATIENTSYMPTOMS or similar that has only your
patient number and symptom number.

Then, if a patient has two symptoms, they get two records added to that new
table. If they have 5 symptoms, they end up with five records.

This is called a many-to-many relationship.
Thanks for your reply.
Click to expand...
[quoted text clipped - 11 lines]
Click to expand...
 
If you have them in a separate table as suggested, now ther\y are no longer
checkboxes.

You now would create a subform within your bigger form to house the
symptoms.

The subform would allow the user to add one or more symptoms. I'd do them
as drop-down combo boxes.

You don't use checkboxes any more, you select the item from a list. This
list is created from the entries in your tblSymptoms and can be expanded
when you need to create new symptoms.

For an exmaple, look at the Northwinds database that comes with Access.

The "Orders" form allows you to create an ORDER. The subform lets you add
one or many products to the order. In your particular application, you
would probably only have one or two fields in your subform. The main one
would be a drop-down where the user could select a symptom (by name most
likely) the symptom number and the main form's key (LogNum?) would then be
stored.


--
Rick B



Elise R via AccessMonster.com said:
You're right Rick, I created the checkboxes. I now have three tables.

tblReaction
LogNum
ReactionDate
Where (3 options)
Type (2 options)
When (3 options)
Symptoms (I listed nine separate symptoms)
Comments

tblSymptoms
Created as you suggested

tblPatientsSymptoms
Created as you suggested

If I change an options in one record, the option gets changed in all the
records. Also, the Where, Type & When and Comments are not being updated in
the table. Surely, I'm missing something that's very simple...


Rick said:
You can't just turn them into checkboxes.

An option box stores ONE value in ONE field.

You will need to add eight more fields. Each one named a symptom.

BUT, that is technically poor database design. Instead, you should have a
brand new separate table called SYMPTOMS where you create a separate record
for each symptom and a number to identify that symptom.

You add a third table called PATIENTSYMPTOMS or similar that has only your
patient number and symptom number.

Then, if a patient has two symptoms, they get two records added to that new
table. If they have 5 symptoms, they end up with five records.

This is called a many-to-many relationship.
Thanks for your reply.
Click to expand...
[quoted text clipped - 11 lines]
one symptom. Is it possible to choose more than one option from a group of
nine?
Click to expand...
Click to expand...
Click to expand...
 
I tried using a drop-down combo box and can only pick one symptom per record.

Rick said:
If you have them in a separate table as suggested, now ther\y are no longer
checkboxes.

You now would create a subform within your bigger form to house the
symptoms.

The subform would allow the user to add one or more symptoms. I'd do them
as drop-down combo boxes.

You don't use checkboxes any more, you select the item from a list. This
list is created from the entries in your tblSymptoms and can be expanded
when you need to create new symptoms.

For an exmaple, look at the Northwinds database that comes with Access.

The "Orders" form allows you to create an ORDER. The subform lets you add
one or many products to the order. In your particular application, you
would probably only have one or two fields in your subform. The main one
would be a drop-down where the user could select a symptom (by name most
likely) the symptom number and the main form's key (LogNum?) would then be
stored.
You're right Rick, I created the checkboxes. I now have three tables.
Click to expand...
[quoted text clipped - 40 lines]
Click to expand...
 
Back
Top