View Single Post
  #45  
Old May 24th, 2006, 05:13 PM posted to microsoft.public.access.tablesdbdesign
external usenet poster
 
Posts: n/a
Default I think I'm almost there...except for...

WeekID (PK) (You cannot make this a true week-of-the-year number, and
also have it as the primary key. Your database fails with this particular
field alone. As soon as you start putting in data, that should become
obvious.)

My note: WeekID is in the xx/xx/xxxx format.


scubadiver, no matter what format WeekID is in, if it is declared a primary
key, then it is required to be unique. If you attempt to use the same WeekID
for two employees, the database will bring up a warning, and not allow you to
do that. So, how are you going to handle having more than one employee per
WeekID?