The values in neither column are unique, but the
combination of the two values is unique. Therefore I
cannot acess the second column by linking through the
first. The user must have human intelligence and local
knowledge in order to select the right pair.
I suppose I could put the pairs in a table and add a
primary key. Then, as you say I could store the number in
the table and look up both the values when I need to
display them.
However, as time goes by the user may generate new pairs
that are not on the list. Then I need to capture the new
info and put it on the list, which adds another level of
complication.
I can base a combo box on the current values of this
table, have the user select one and enter that value into
the current record, current field. If the user doesn't
select a value he can enter a new one, which will appear
in the combobox next time. Why can't I do that with two
values and two fields? If the pair exists, select it and
store both values in the respective fields of this record;
otherwise enter your own data.
What you say is more "Database Correct", but sometimes it
doesn't make sense. If I go your route, then every time I
look at a table all I see is a bunch of key field numbers.
In order to make sense out of the table I have to go make
a bunch of queries to turn all the links back into a flat
file temporarily, just so I can see the data. Constructing
all the links and keeping track of them may take more time
and space than just storing the (admittedly redundant)
data.