What did you post? Is that your existing database or your attempt at normalization?
I suggest you read up on normalization and work througha few tutorials (https://www.w3schools.in/dbms/database-normalization/
Here's what I see wrong with what you posted:
1. All those tables with just peoples' names should be combined into a 'Role' table. It would be structured like this:
Steve Smith, Clerk
Steve Smith, Technician
John Davis, Clerk
Barry Miles, Repairmen
That elminiates all tables named after a role.
2. Improper use of foreign keys. You went through the trouble of setting up lookup tables with their own ID fields, but then you don't use those ID fields. For example, You have a Customers table and you have a Customer field in AFRs--so far so good. But in the AFRs.Customer you are storing the text value of Customer table, not their ID from the Customer table. That is incorrect. You should be using the ID value of Customer in AFRs. That's just one example, you do this a lot.
3. Storing values in field names. In AFRs, [12ASpec], [91ASpec] & [93ASpec] should not be field names, they shoudl be values in a field. Those fields need to be taken out of AFRs and put into their own table. It would look like this:
SpecID, autonumber, primary key
ID_AFRs, number, foreign key to AFRs.ID record that spec value belongs to
SpecType, number, this will hold the 12, 91, or 93 that is now in the field name
SpecValue, ?, this will hold the actual value you are putting into those 3 fields right now
Thats how you should store that data, not in 3 fields in AFRs named after their type. I don't know your data, but I suspect you've done this in more than just those 3 fields.
I suggest you read thru the link I gave above, make the changes I illustrated, set up your Relationship tool after you do and then post a screenshot of it back here for us to check.