Auto-populate a text field based on a checkbox

[tutlay]

Hi all -- new here and to Access 2007. I hope this post finds you well.

I have a database with the following 2 fields: (1) Ineligible, checkbox; and (2) Active/Inactive, dropdown menu. When a participant is deemed "Ineligible", staff clicks the checkbox AND is supposed to be checking the "Inactive" option. I find that this is redundant. I'm sure there's a way to autopopulate the text box with "Inactive" when the "Ineligible" box is checked (vice versa with active/eligible).

How can I connect these two fields to do this task automation?

[RuralGuy]

Normalization rules state that fields within a record should not be dependent on one another.

[June7]

I agree with RG.

If participant cannot be Active and Ineligible at same time, why bother with 2 fields? Status is either (Active and Eligible) or (Not Active and Not Eligible)? The two fields appear redundant.

However, if you must, would require code.

[tutlay]

Thank you both, RG and June7. I do recognize that this is a redundant work (so unnecessary!) but bosses want me to do that. I was thinking of another way to lessen manual work. So when a staff member checks off "Ineligible", they're supposed to uncheck the "Eligible" box -- can I auto-uncheck the "Eligible" box when the "Ineligible" box is checked? So that only one of them is checked at any given time.

[RuralGuy]

Why not use an Option Group?

[Xipooo]

You could also do make it a calculated field on your table which just matches the check box value. When the checkbox is updated just do a me.requery on the table. Probably the least amount of hassle.

[June7]

Xipooo, OP shows Access 2007 which does not have Calculated field type.

tutlay, I am confused by your last question. An option group as RG suggests is great to set value of a single field but you originally said you have two fields, one dependent on the other.

[Xipooo]

Xipooo, OP shows Access 2007 which does not have Calculated field type.

tutlay, I am confused by your last question. An option group as RG suggests is great to set value of a single field but you originally said you have two fields, one dependent on the other.

Good catch. I forgot that it wasn't available in 2007. Knew it wasn't in 2003.