Problem with subordination and forms in Access, how to solve?

Question

Database design

Good afternoon! I create a database in MS Access: there were a number of problems. Unable to create subform "General" + "Type of equipment" + "Departure". If I understand correctly, this is for the reason that there are connections 1-1, and not 1-many. The question follows: how to change the tables in order to obtain the necessary form and type of subordination?
It is required that one equipment type from the Equipment Type table has many rows from the General table, but the one-to-many option is not available for selection. Similarly with the links of the tables "Departure" and "General".
"General" should also have a similar connection with "Depot", but it does not work out.
The essence of the table: a database of a company that coordinates repairmen and depots. Each depot has certain equipment (two depots can have two of the same equipment) and each depot is part of a certain ARC. Those. one depot can be in only one VRC. Also, each depot has its own repairman, who can go to other depots, but only he goes to this depot.

Answer 1

Of course it's not available because in both cases it's the primary key. Why does the General table have such a complex composite primary key? Why does it already have an equipment type - but also a link to the equipment type table?
At least it's redundant. At you in the table "common" field Code_TO should not be a primary key. The field "type of equipment" is generally to Allah, it is not needed, because there will be a link to it.
In the "equipment type" table, the equipment type field should not be the primary key either. But Kod_TO is the primary key unambiguously. And now you take it with the mouse and throw it on the "General" table - then you will just create the "one-to-many" type.
The data scheme itself... Leaves much to be desired, of course, the best. Why in the "departure" - repair_code - is not the primary key, but the repairman, i.e. text field with last name first name, primary? It should be exactly the opposite.
Why is the depot code not the primary key in the depot, but the Depot_Name and VRK_Code are made the primary key? Etc.