Are you trying to keep track of which person has which computer? If so, I don't think you need a third table. You should be able to have a computerID field in the Person table or put a personID field in the computer table, depending on whether 1 person can have more than one computer of 1 computer can have more than 1 person.
If you do need to assign many people to many computers, here's a demo file that assigns companies to contracts in this fashion you can take a look at:
Thanks Mark and Phil :-)
First Mark, I do need the third table to keep the base strictly relational.
Second Phil, my three tables has exactly the same table structure as in your example. So you confirm that I´ve got the structure right.
But my question was how do I
if I am restricted to import records into one table at a time, how will the data show up in the third table, (your Contract_Company table). I have imported computers and persons into table one and two (corresponding to your Companies and Contracts tables) and naively expect my third table to join the people with the PCs (again corresponding to your Contract_Company table). The third table contains only the two key fields from table one and two, trying to link the users with their PCs.
is it possible to import records from an external Excel sheet into fields in different tables in one go (I know how to import into fields in ONE FM table)
I don't confirm that you have the structure right. I suspect that you do not need a join table here. (And your database will still be relational.)
If you try out the demo file, you'll find that you can add records directly to the join table via a portal.
But it still seems that you really need this relational database structure:
People::PeopleID = Computers::PeopleID
You only need the join table if you will have a list of multiple people assigned to the same computer AND also a list of multiple computers assigned to the same person.
As Phil stated above the only reason for a third table is if you have more than one person per computer and more than one computer per person.
As for importing data into 3 tables from one (or multple excel files) it would take a separate import for each table or file. You could probably write a script to do it in one step, but it would take longer to write the script than to do the imports. That would be worthwhile if it was an import that you would have to do over and over, but if it is a one time thing.........
If your excel file has the computerID, computername, personID, personName on each line. You could do the import for the computer table to get the computerID, computername and personID fields. Then for the person table import the personID, personname and computerID fields. Then you can set your relationships to be either by computerID or by personID depending on what you need.