I would need to know more about the relationships between these tables. What are they? The names aren't very meaningful. Are they one-to-many relationships? For example: Customers to Orders to Order Details to Products. Four tables. Each has a primary key and the last three have a foreign key pointing to the parent. Watch Relationships.

If you're trying to say that the other tables have a NATURAL KEY (like a vendor part number, or phone number, or SSN - something that exists in the real world) that is being used for the relationship, then you could just add an AutoNumber field to the parent table, add a Long Int as a foreign key to the child table, and then use an Update Query to copy that info. If that's where you're going, then yes, that would make a cool video. I've had other students ask me about this before. I'll add it to the list.

Sorry, I just saw that I could attach an image. So what we want to do is add an autonumber to an existing table that doesn't have an autonumber. then repeat for two other tables. I'm not sure of the order to do things or how:
1) add an autonumber to the Cntry table (Country)
2) change the foreign id (BirthCntryId) in the Entity table from the old Id to the new autonumber id now found in the Cntry table.

Then we repeat adding an autonumber to RegSub and change RegnSubId in the Cntry table to the new autonumber id.
Then we repeat adding an autonumber to Regn and change  RegnId in the RegnSub table with the new autonumber id.

I'm wondering if we can build a query to do this, one for each parent file.

Update Queries

To understand an example of the hierarchy,
Entity John (AID = 15) was born in Canada (ISO cd and the ID in Cntry = 124).
Canada is part of North America (ISO cd and Id in Regnsub = 21)
North America is part of the Americas (ISO cd and Id in Regn = 19)

All of the primary key ids (124, 21, 19) are going to remain as data columns in their respective tables, but we will change the foreign ids to the new autonumber primary keys.