Error in tables

[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













Thanks!

[June7]

Your images are not showing for me. Did you just post a link to a fileshare site? I am blocked. Images can be embedded in post.

Does [personal data of employee] have multiple records for each employee? If not, can probably just be one table.

[Hello1]

I didnt understand ur question really, pretty unexperienced in this yet
Hope u can understand it from the pictures which i uploaded directly now.

[June7]

Sounds like you need a better understanding of relational database principles. Maybe this tutorial site will help http://www.rogersaccesslibrary.com/

Again, what is nature of the table relationship (1-to-1, 1-to-many, many-to-many)? Will Personal have multiple records for each employee?

Regardless, the table link is wrong. Should be saving ID_Employee PK value as a FK in Personal.

[Hello1]

Hey june, thanks again.
The relationship was 1 to many but i tried 1 to 1 and got same. "Will Personal have multiple records for each employee" I want that each employee has his personal info in the personal stuff table. Actually because i didnt want to put all the records in employee table (to have it more clear), i wanted to make few lets call them "sub tables" of the employee. So i wanted for example to make a table similar to Personal, one which has records about the employee job (salary, insurance, hire date...).
Here a new one, i exchanged job which a mistake in the first picture.

[June7]

Unless you care about history of employee phone/address/email, I would not split the employee personal info into two tables. Employee and Personal Details should be one table.

Assuming employee could have more than one job (promotions, rehires) then you need another (junction) table that documents this job history, something like:

tblEmpJobs
EmployeeID (foreign key)
JobID (foreign key)
EffectiveDate
TerminationDate

This table is the link between employees and jobs. Did you review the tutorial link I referenced? I suggest it would be a valuable exercise before you continue db development.


Advise no spaces or special characters/punctuation (underscore is exception) in naming convention - and that means no () in field names.

[Hello1]

I did take a look but no idea where to start
Thanks for the advices, i might try the junction.

[June7]

Why not start with the Tutorials link on Roger's page?