New people added in table 1 not showing up in other tables despite relationship

m33r4

Registered User.
Local time
Today, 23:31
Joined
May 5, 2013
Messages
11
I have 3 tables.

Table 1: contains staff names and contact numbers
Table 2: contains training above staff have been on or need to go on
Table 3: contains pc and printer asset numbers of above staff

I used a form and entered some new members of staff in table 1. They got their auto numbers etc but when I open table 2 and table 3 those new members are not showing up in those tables. I have checked the relationship status between the 3 tables and the staffID from Table 1 is associated to table 2 and to table 3.

Any ideas what's stopping the new entries from showing up in tables 2 and 3 please?

Thanks.
 
Attachment: showing relationship
 

Attachments

  • relationshiptable.GIF
    relationshiptable.GIF
    78.7 KB · Views: 120
Imputing data into a table doesn't populate other tables just becouse of the relationship created betwen the two tables. I think you have this all wrong.
 
I think your table structure is wrong.
Table staffAssetID_table should not have the actual staff name fields, just the the field that links the two tables.

The staffTrainingID_table should be replaced with two tables becuase you have a many to many relationship between the staff table and the training courses. This kind of relationship is uses a third table. You already have a staff table. You need a table to hold details of training courses. It should not have a field for each course. It should have an ID field and a field for the course title with entries in the table for each course.
The other table would just need a number field the CourseID number and a number field for the StaffID number.
There are countless posts and web pages on this subject. eg: http://ms-access-tips.blogspot.co.uk/2011/04/many-to-many-relationship.html
Have a read. Post back if you still need help.
 
.....You need a table to hold details of training courses. It should not have a field for each course. It should have an ID field and a field for the course title with entries in the table for each course.
.....
Thanks for the input. I am sorry to be troublesome, but only in my 3rd day of using Access. I have read the blog link but am none the wiser how to apply this to my tables :o

Although I understand to split the 1 training table into 2 tables, I don't quite grasp how I need to list the different training courses if not in separate fields? I need to run queries about which staff member has taken training in e.g Fire Awareness perhaps, or in Risk Assessment.

I also need to see all the training in a list form for reports perhaps.

Sorry for my ignorance, someday I will get it :banghead:
 
Although I understand to split the 1 training table into 2 tables, I don't quite grasp how I need to list the different training courses if not in separate fields? :banghead:

You need a Table that only lists Training plus some info on that particular type of training.

Think about what would happen if the Training grew by another two items. or perhaps 20 or even 200. Your design would not handle this growth. A separate table would.

You have Forename and Surname in every table. A data base means do it once.
 
You need a Table that only lists Training plus some info on that particular type of training.

Think about what would happen if the Training grew by another two items. or perhaps 20 or even 200. Your design would not handle this growth. A separate table would.

You have Forename and Surname in every table. A data base means do it once.
Table 3 is the training only table - I shall remove the forename and surname fields.
 
Can you use Table names instead of Table 3 etc.

That leads to confusion.
 
Can you use Table names instead of Table 3 etc.

That leads to confusion.
If you refer to the link I have posted in the original question, I have used name across all 3 tables.

Thanks.
 
Let me rephrase my question.

Which table is which.?????

Is table 3 the one in the middle the left or right. Guessing is not the best thing to do in programing.
 
I should have also asked you if you understand why I asked you to get rid of the repeating fields Forename and Surname.

If you don't fully understand then please say so. It is very important that you understand. This Rule is one of the top ten in database design
 

Users who are viewing this thread

Back
Top Bottom