Combo box value not populating table

[Guest]

I have 3 Status values that the user can select in a combo box on a form. 1)
Not Worked 2) In Progress 3) Resolved. Once the user selects the desired
value and has completed other components of the form, they click a command
button on the form that says "Save & Close Entry". I want the value they
select in the combo-box to write to the Entry table. I have the Entry
table's Status field as the control source. And made a values list for the 3
options they can select in the record source property of the combo box. What
do I need to do to get the Status value they select to populate the Status
field on the Entry table? Any ideas or different approaches are much
appreciated.

 

[Guest]

Where I said record source, I meant row source.

I set the RowSourceType property to
ValueList, and set the RowSource to a string containing the list of values,
separated by a semi-colon.

Question # 2: Should I even be populating my combo box this way or is it
better design to make a small table holding these 3 possible Status values?

 

[Rick Brandt]

Where I said record source, I meant row source.

I set the RowSourceType property to
ValueList, and set the RowSource to a string containing the list of
values, separated by a semi-colon.

Question # 2: Should I even be populating my combo box this way or is
it better design to make a small table holding these 3 possible
Status values?

Writing to the table is controlled by the ControlSource. The RowSource has
nothing to do with that. All that does is give you the list of choices.

 

[John W. Vinson]

Where I said record source, I meant row source.

I set the RowSourceType property to
ValueList, and set the RowSource to a string containing the list of values,
separated by a semi-colon.

The RowSource is where the data comes FROM. The Control Source is where the
data goes TO. It should be the name of the status field in your form's
Recordsource table or query.

Question # 2: Should I even be populating my combo box this way or is it
better design to make a small table holding these 3 possible Status values?

I generally use a table - it's much easier to edit if anything needs to be
added or changed. The only exceptions would be fields with very few values
which will never, over the life of the application, need to be changed - e.g.
Sex; or yes/no fields with a combo box control.

John W. Vinson [MVP]

 

[Guest]

Good point as to why to use a table! My list of choices "could"
theoretically change. I would hate to have to change it on every form that
may use that list if it were to expand. Thanks for giving me just what I
needed to decide whether to use a table or put a list in the row source!

 

[Guest]

I was only correcting my wording from my original post so that no one would
think I meant record source. Thanks.