Tables dont want to work

[Hello1]

Hello there.
As u gonna see in the next pictures, im not able to make any records in the table "employee". I guess the relationship i made between "employee" and "personal data of employee" is wrong. So my question is, is there a way to connect these 2 tables or should i put everything from "personal data of employee" in "employee" table. Im a newbie in this :banghead:

postimg(dot)org/image/qrk90dsi5/
postimg(dot)org/image/skn5opdot/
postimg(dot)org/image/njfrnc68d/
postimg(dot)org/image/6mqouwyod/

Please, i cant post images yet coz im new here, just delete the "(dot)" and put a real dot
and if someone can please post them coz i cant, thanks!

 

[gemma-the-husky]

there you go

www.postimg.org/image/qrk90dsi5/
www.postimg.org/image/skn5opdot/
www.postimg.org/image/njfrnc68d/
www.postimg.org/image/6mqouwyod/

 

[gemma-the-husky]

it would be easier to see your relationships diagram, I think.

 

[Hello1]

Hi, thanks.
The relationship is in the third picture, if thats what u mean. The relation was 1 to many, i tried 1 to 1 but got same.
I wanted to make a database of an employee. Besides the employee table, i wanted to make few other tables like his personal details, his job (whats he doing, his salary, how many hours he worked and how many he didnt..) and to connect them to the employee table. The reason i wanted to do it, is to not have too much data in the employee table, but seems it isnt really possible? :/

 

[gemma-the-husky]

right.

you only need one table, I think all the data in the second table could be in the first. If you really want to keep the salary data private, then this is one of the occasions that a 1:1 table might be useful.

the way you have it, you could have several personal details records per employee - but it should still work. In this case though, you need a value in the subtable, to reference the EMPLOYEE_ID in the main table - the other way to the way you have it.

 

[Hello1]

Made a mistake in the first pictures. The Personal table should actually be called "Job" . However, so seems the simplest solution for me is to delete and put both tables (Job and Personal details) into employee table.

 

[plog]

First, I'd remove all special characters and spaces from all your names. This will make coding and communicating about your data more difficult. Then you need to get rid of the [Personal details] table. Its data should be in the Employee table.

Also, tables with 1 real field for data (autonumber primary keys aren't real data) shouldn't exist. That means your gender table needs to go.

That's just things that I can see based on your picture. There may be more issues that no one on this forum can identify because we don't understand your data. It would help if you could give us an explanation of the real-world process this data is to model. Don't use database jargon or describe what you hope to accomplish with Access--just explain to us what it is your organization does.

 

[Hello1]

Hi plog, thanks for the answer and time.
My goal was to make a small human resources management database. Wanted to have the main table "Employee" (which contains his name, surname, department, phone number, email, address and so) and 2 sub tables "Job" (Which contains the salary of the employee, the date he was hired, how many hours he worked, how many he didnt and so on) and "Personal details about employee" (which contains basically his personal stuff. Like where is he born, the date of birth, the country/city of birth, his nationality and so on) . Those 2 r actually all about employee which i guess could be in Employee table and not separated but to make more space and more clear and wanted to try and make those 2 tables. The gender table works fine, im using it as combo box and when i fill out data in "Personal details" table the gender offers me in combo box M (male) and F (Female) what i actually wanted. Also few more small "encrypted" tables like gender.