I think I'm almost there...except for...

[mnature]

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?

 

[mnature]

Jamie, you are bringing up some good points. Speaking of normalization as if
it were a self-evident expression is certainly not helping people.

However, there are a number of posts to this forum, where it is obvious that
these people have no experience in programming Access other than the ability
to click on an icon to open the program. Isn't it fair to say that if they
are sent off to search for information about normalization, that they will
probably stumble across other information about programming databases, and
thus become better able to do whatever project they want to do? In the case
of scubadiver, it would be better for everyone if he would go out and buy a
few beginner books about Access, and then actually read them.

I would like to ask you directly, then: What is the best way to talk to
someone who seems to be rather clueless about databases? Some people seem to
respond quite well to being told to study the subject, and come back a few
days later with some excellent questions. Some people respond well to actual
samples of what we think they need (learn by example). Some can be told to
think of each table as a separate subject, and intuitively grasp the concept
of normalization through that.

I look at it as a graded approach to the problem, depending on how the
problem is presented. Someone posts some tables, you mention they are in
need of normalization. They come back with different tables, and you realize
they have no idea what normalization is, so you tell them to go learn
normalization. They come back with even different tables, that are an even
worse design, so you post what you think their tables should look like
(basing that upon whatever clues they have given about what they are trying
to do). You also try to explain, in simple terms, what is meant by
normalization. By this point, they usually are starting to understand. But
not always.

So, is there a better way to proceed?