suggest a minimum of three tables:
tblReps
RepID (primary key)
FirstName
LastName
(any other fields that describe a rep)
tblRepAbsences
AbsID (primary key)
RepID (foreign key from tblReps)
DateOfAbsence (don't use the word "Date" as a fieldname)
Reason
tblServiceLevels
LevelID (primary key)
ServiceLevel
ServiceDate
i assume you calculate the service level based in part on the number of reps
who actually work a given day or shift - but i also assume the service level
is a daily (or per shift) *company* value, not tied to a specific rep being
absent. since that number is not directly related to a specific rep or
specific absence record, it doesn't belong in either of the first two
tables.
it's also possible that the service level can be calculated entirely from
data that are entered in the database - in which case you may not need to
save the service level as hard data at all, but merely calculate it when
needed.
you need to forget about forms and reports for the moment, and figure out
what data you need to put in the database, and how that data are related.
then create your tables/relationships. that's your foundation; once it's
built correctly, you can build the rest of the database (queries, forms,
reports) on top of it. creating properly normalized tables, and
relationships, is no small task. for information to help you accomplish it,
suggest you take a look at
http://www.ltcomputerdesigns.com/JCReferences.html
focusing on Starting Out, and Database Design 101, links.
hth
