Armen,

Great point! It is true no referential integrity, just to prevent typos!
Glad you brought that up, jump in anytime!

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm
"Armen Stein" wrote in message
...
On Tue, 26 Jan 2010 15:29:17 -0500, "Gina Whipp"
wrote:

--Do I need to create a CityID table? I have CityID a few places in
different tables but haven't created a CityID table yet.

***I use one because you'd be surprised how many typos people can make when
typing their own city name. So yes, you need a City table should you
decide
to go that route OR you could change it to CityName and let people type.

I'll just jump in briefly with a suggestion.

Cities are one of the very few tables for which we don't link with
foreign keys or enforce referential integrity. As Gina suggests, we
just let people type in the City name - it becomes data-entry
assistance rather than a rigid relationship.

- we create tblCity
- we create relationships from any table with an address to tblCity
using CityName, without enforcing referential integrity.
- on our forms, the City combobox helps users remember the spelling of
the city and type it in faster.
- the City combobox traps for NotInList and silently adds a new City
on the fly.
- we build a simple admin screen to allow the user to delete incorrect
cities. They should also find and correct those cities in the address
tables.

Cheers,

Armen Stein
Microsoft Access MVP
www.JStreetTech.com