Using combos on the forms for the lookup values is standard practice. For a
report, where you use textboxes rather than combos, you need to base the
report on a query so that you can join the main table to the lookup tables.
Select the text fields rather than the id fields. Use left joins for all
the lookup tables if you have defined them as optional otherwise you will
miss rows from the main table if they have no value in the lookup field.

NEVER remove RI to "make it easy to input data". If you have trouble
inputting data with RI turned on, you have issues you need to deal with. RI
is necessary to ensure certain types of data validity. You can try to
control it yourself with code (many others have and been sorry they did) but
I don't recommend it. Always let the RDBMS enforce RI wherever you can.

"IrenaY" wrote in message
...
I understand that I need to build table relationships based on IDs, not on
text values that may change over the life of the database. I have read in
this discussion group the perils of value lists in a table. Here's my
situation:

One foundation table named TBL_Project has eight fields in it that are
FKs
(number), linked to small "reference" or "feeder" tables, and the only
things
these individual tables have in them are PKs (autonumber) and their
descriptions (text). When we data enter, we need to see the descriptions
on
the forms and on the reports. All eight fields will be data entered on
one
form.

In addition, I presently have a one-to-many relationship but have played
around with not enforcing referential integrity in order to populate other
fields in TBL_Project. Prior to taking off the ref integrity, I checked
to
see if the field was required or not.

So, my queries a How do I see the values, not the IDs?
And
Is it okay to not enforce ref integrity in order to populate the rest of
the
data in the foundation table? It would help if you took me through it
slowly
if it involves any code, I'm not quite there yet.

Thanks.

Irena