"=?Utf-8?B?d3N0b2thcno=?=" wrote in
:


WorkOrders(*WONumber, SizeOfJob, DateOrdered, etc)

Items(*WONumber+, *LineNumber, DesciptionOfItem, CostOfItem, Width)

Layers(*WONumber+, *LineNumber+, *LayerCode, Transparency,
Thickness)


I cannot use a primary key in
the Item table and the Layer table. I must be able to have many
entries of the same Work ID In both the Item Table and Layer Table as
well as many items and layers.

It is frustrating when people give no evidence of having read the replies
to their questions. If you actually do look at the suggestion above, you'll
see that Items has a PK made up of (WONumbner, LineNumber) which means that
you can have as many Items as you like with the same WONumber as long as
they have different LineNumbers. Similar with Layers.

I'd like to take you back over something else in my reply:

If you are finding this hard, you might like to read some basic
grounding in R theory and database design. You will really need to
understand this stuff in order to get anything useful out of Access.


You really have to understand what a table is, what a PK does, how to make
relationships etc to do anything useful with Access. It's a very different
beast from the rest of the Office package, which is why it's not included
in Office Standard -- at last MS got the message that it's unsuitable for
naive end-users, unlike Word and Excel. IMO, I have sat through so many
teeth-grindingly awful Powerpoint presentations, I am starting to think
that it should be withdrawn to Office Professional too...


Currently in my junction table I have Work ID, Item Num, LayerNum.

This appropriate only if you have a situation where a Layer can be applied
to a WorkOrder any number of times, but only once for each Item -- although
I don't know much about what you are trying to model, I would find it hard
to visualise how that would be a good scheme.

All the best


Tim F