> . . . However, when I try and create a
> lookup table, it deletes the records
> of gives me an error indicating I am
> putting in an unexpected value. . . .
If you mean "when I try and create a Lookup Field," just don't do that. You
already have your lookup Table, you can join the Tables in a Query andReference:: Sikh Philosophy Network http://www.sikhphilosophy.net/information-technology/11862-createing-look-up-field.htmlReference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11862
display the text instead of the ID, it works nicely with the Combo Box, and
there's no question what data you have in which table.
Lookup Fields, on the other hand, are a violation of relational design
principles -- they obscure what is actually stored in the Table by
displaying something else in Table View, and they can be a real pain when
you do Queries.
Microsoft Access MVP