Correct table relationship?

[BartK]

Hello all,
I am in the beginning of setting up a database and have NOT messed with multiple tables. I just want to make sure that I am setting up the tables as well as the relationships correctly.

Here is what I currently have, 4 tables and they are named. Employee, phone, radio and spotter. Employee table is where my primary key is located and I currently have a 1-to-many relationship between Employee and the others.

What I want to be able to do is to store information in the multiple tables from 1 form, which I don't think will be an issue and then at a later date be able to pull up information. EX.

John Doe
Employee number 24
given radio 35 and phone 78.

Thus being able to skip anything being put into the spotter table. Then at a later date be able to pull up only the select information I originally put it? Am I on the correct path? Thanks for the advice.

 

[MarkK]

Every table should have a primary key. Make it the first column, and make it an autonumber. I name the field after the table, and append ID, so tblPhone's PK is PhoneID. tblSpotter's key is SpotterID.

I currently have a 1-to-many relationship between Employee and the others.

This means that one employee can have many phones, many radios, and many spotters. Is that what you intend?

What is a spotter? Is that a person, another employee?

hth

 

[BartK]

A spotter is a Multi-Gas Detector, Minning Industry.

 

[David R]

Just because a table has a relationship to another table does not mean a query HAS to utilize all the connected tables. Drag just your Employee, Phone, and Radio tables into a query, and make sure the relationship lines are correct. Run it and you'll see what I mean.

 

[Pat Hartman]

Since the relationships are 1-many, you should be using three subforms on the main form. One for each of the many-side tables.

 

[BartK]

Thanks for the replies. I will try that here in a little bit. Let you know what I come up with.