G
Greg
Hi,
I am trying to set up a system that tracks employee vacation usage. Our
employees accrue 5 days vacation after every 2,000 hrs.
I have set up two tables. The first table, I call EMPLOYEE table.
EMPLOYEE table consists of the following fields:
SS# (Primary key)
Employee Name
Employee Type
Start Date
End Date
Yes/No
The second table I called VACATION LOG.
VACATION LOG table consists of the following fields:
SS# (Foreign key)
Employee Name
Hours Taken
Date Taken
Week Ending Date
My question is this, I have a primary key (SS#) in the EMPLOYEE table and a
foreing key (SS#) in VACATION LOG table that relates them. But I do not have
a primary key in the VACATION LOG table. Is it possible not to have a
primary key in a table? I have thought about using the EMPLOYEE ID as a
primary key in the VACATION LOG but I am unsure of what use that would be
since I have already used the Employee SS # as an identifier in the EMPLOYEE
table.
I would appreciate any helpful insights on how to go about this.
Thanks
I am trying to set up a system that tracks employee vacation usage. Our
employees accrue 5 days vacation after every 2,000 hrs.
I have set up two tables. The first table, I call EMPLOYEE table.
EMPLOYEE table consists of the following fields:
SS# (Primary key)
Employee Name
Employee Type
Start Date
End Date
Yes/No
The second table I called VACATION LOG.
VACATION LOG table consists of the following fields:
SS# (Foreign key)
Employee Name
Hours Taken
Date Taken
Week Ending Date
My question is this, I have a primary key (SS#) in the EMPLOYEE table and a
foreing key (SS#) in VACATION LOG table that relates them. But I do not have
a primary key in the VACATION LOG table. Is it possible not to have a
primary key in a table? I have thought about using the EMPLOYEE ID as a
primary key in the VACATION LOG but I am unsure of what use that would be
since I have already used the Employee SS # as an identifier in the EMPLOYEE
table.
I would appreciate any helpful insights on how to go about this.
Thanks