Update a column in table

[Ken Sheridan]

I'll be waiting how your next version will be.

Here's the amended file. It now caters for a city's being in two or more regional units, e.g. Kansas City being in Kansas and Missouri. If a user enters a user enters a new city name, the combo box's NotInList event procedure now includes code to determine if a city of the same name currently exists in the database in the same country but a different region. If this is the case it opens a dialogue form listing the city or cities in question, and prompts the user to select one of the listed cities if they are referring to that city. If so a new binary relationship value is created between the existing city and the different region.

If, on the other hand, the user does not select an existing city then a new city of the same name is inserted into the Cities table, and a relationship between that city and the different region is created.

To cater for two or more 'cities' (the term is used here to denote a nucleated settlement of any size, and includes distinct small towns like my own location here in Newport, Shropshire), of the same name existing in the same region, rather than introducing a sub-regional entity type, e.g County in the USA, I've simply included the county or equivalent name in the City column in the Cities table to overcome the ambiguity. The example I've used in the dummy data is one of the five Springfields in Wisconsin. I can't immediately think of any UK parallels to this, but I would not be surprised if there is a UK county with more than one Walton, which is a very common place name, derived from the Old English wealh-tūn, and referring to a settlement still occupied by native Britons after the Anglo Saxon migrations into the country.