Hi,

If TableA is like:

City,    State,    Country    ' fields name
NewYork, NewYork, US
LosAngeles, California, US
Chicago, Illinois, US
Paris, IleDeFrance, France
Monterrey, Nuevo Leon, Mexico

if TableB is like

Country, Continent '  fields name
US,    NorthAmerica
France,    Europe
Mexico, CentralAmerica

You can change Chicago State to Alabama, if you wish, that won't change
anything, anywhere else, but if you change its country to France, then its
continent would be Europe. The idea of the relation is to place what is
dependant in the same table, such as US is in NorthAmerica, and France is in
Europe, or LosAngeles is in California, in US. Sure, you can add a record
like

Paris, Texas, US

but that Paris will now be in NorthAmerica.

If you change, in tableB, {US, NorthAmerica} to {US, America}, by virtue of
the relation, all cities, in tableA, with the mention  country=US, will now
have their continent = America, through the RELATED tableB.

So, maybe you have to change your table design to "regroup" the properties
(columns) together, in the relevant table.

(Note that TableA design, here, is not really good, since, in theory, having
the state, I can have the country, so another table should have been
created, probably, but that was just an example).

Hoping it may help,
Vanderghast, Access MVP

What information exists in the Product table to identify which records
need to be updated? You can see your database; we cannot! Since you
don't say how you'll be identifying which records to change, nobody
can help you come up with the Query!

                 John W. Vinson[MVP]