look up tables

  • Thread starter Thread starter JL
  • Start date Start date
J

JL

When using a lookup table with only one field, is it necessary to add
an additional field to be the primary key, or can the field itself be
the primary key? For example, for a list of state abbreviations where
they are never the same, could the Field with the abbreviation be the
primary key?

Thanks,
JL
 
JL said:
When using a lookup table with only one field, is it necessary to add
an additional field to be the primary key, or can the field itself be
the primary key? For example, for a list of state abbreviations where
they are never the same, could the Field with the abbreviation be the
primary key?

Thanks,
JL
Click to expand...

Sure. If the single field is unique and stable then I see no point in
having a surrogate key field. Others use them all the time no matter what.
It's kind of a personal preference issue.
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Lookup table, have item #2 out of 3 appear in form? 3
When to Use Long Number and when to use text as a Primary Key? 1
Showing un-matched fields in a basic query 4
MS Access Avoiding redundancy 1
Primary Key Cascade Question 5
Combine number in a Table field 1
generate primary key by expression 5
Counting Values in a Range of Columns 7

Back
Top