View Single Post
  #8  
Old May 23rd, 2006, 03:09 PM posted to microsoft.public.access.tablesdbdesign
external usenet poster
 
Posts: n/a
Default I think I'm almost there...except for...

You MUST learn about normalisation that is where you a going wrong.

You have ignored at least a dozen previous responses suggesting this course
of action from various people.

My comments were constructive and too the point.

Over 90 Posts from you in the last and who knows how many answers from
people trying to help you and still you won't invest your time in learning
the basics.

LEARN HOW TO NORMALISE YOUR DATA.

--
Slainte

Craig Alexander Morrison
Crawbridge Data (Scotland) Limited
"scubadiver" wrote in message
...
With respect, that isn't the most constructive response.

I've tried to learn about normalization as much as I can and I'm getting
very bored and frustrated when I get this kind of answer. I can't see
where
I'm going wrong.


"Craig Alexander Morrison" wrote:

I don't think so....

Suggest you learn about normalisation and then things will just pop into
place.

Access loves a normalised database design; it loves to punish a design
that
is anything but.

--
Slainte

Craig Alexander Morrison
Crawbridge Data (Scotland) Limited
"scubadiver" wrote in message
...
my table relations. From left to right:

"Employees"

Payroll (PK: 1)
Employee
Work
Status
Rate

"week"

Payroll (FK: Many)
month
week (PK: 1)

"dept"

Week (FK: many)
Dept
Subdept
Costcentre
Standard
timehalf
double

So each person has multiple weeks and each week has multiple
departments.

But I get the following message: "You cannot add or a change a record
because a related record is required in table 'week'.

Can someone enlighten me?