in a normalized database, each employee should be listed once in an employee
table. that table would be about employees, not about timecards. certainly i
can't imagine a multi-record table in a normalized database without a
primary key.
you say one employee has many timecards, which i understand (having done my
share of punching a clock). now, what do you define as a timecard? in the
"real world", usually an employee has one timecard each week, with which
he/she clocks in and out each day that he/she works that week. the next
week, the employee gets at new timecard to clock in/out on, etc, etc, etc.
do you need to track each clock in/out specific to each time card? or just
track each employee's clock in/out times by date, without reference to a
specific time card?


"joe" wrote in message
...
How can i get the results of each timecard entry to only appear in the
employee table under the employee number which is unique.It is a one to
many(one employee to many timecards) but i just want the entrys to be under
the one time entry of the employee number not for each timecard and employee
number to be repeated over and over again in the employee table.I have been
told to create the employee number as a primary in the employee table and
not to have a primary key at all in the timecard table but when i transfer
all the fields to a form...i get dups not allowed and i cant enter another
record on the form.What am i doing wrong?????? I am unsure if this is a
forms problem or a design problem with the primary key????