Armen,
I guess I handle mine differently because the End User cannot add a City...
They have to get the *Admin* to add it. (I have a File Maintenance section
that on the *System Admin* can get to. This also prevents
changes/additions/deletions from other tables that have look-up values.) Of
course, I include a City, State and FIPS Code table in all my databases so
the odds of them typing a City I don't have is a zillion to one.
However, unless you have such a table probably better to do it your way!
--
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 19:04:59 -0500, "Gina Whipp"
wrote:
That is what we are suggesting but with the table set up so they can't make
a typo.
Yes. A combobox has a built-in ability to display the whole value of
the first match it finds, which makes data entry much quicker.
However, the way we do it just discourages typos, it doesn't *prevent*
them. If they type a new city name, we add it to the lookup table
automatically and silently. So it's possible to add a misspelled
city. It's just not that big of a deal to remove it later, and we
find that when a correctly spelled city is in there already, people
tend to just use it and not get creative with a new spelling.
You typically need some kind of add-on-the-fly because new cities will
need to be added all the time.
You could prompt the user in the Not In List event to see if they want
to add a new city, but we don't want to slow down the data entry
process. So we just add it in there without asking.
Armen Stein
Microsoft Access MVP
www.JStreetTech.com