Confusion with many-to-one relations

[BDibz]

I'm trying to have each jobNumber have one partID, and each partID to have several electrodeIDs tied to it. I thought that the setup that I have here would accomplish this. However, as you can see, when I look at the parts table, each partID shows all of the electrodeID's and not just the ones that correspond to that part. Why is this? How can I make sure it only is tied to the corresponding parts?

[orange]

BDibz,
It would be easier for readers to understand and respond if you could describe the business activity in simple, clear English. We don't know what a Job involves nor how an electrode relates to a part.

Can you tell us about a Job?
What parts are involved?
And where the electrodes fit in this picture?

I think a simple example might clear things up.

Good luck.

Here is a link to info on Database Planning and design.

[June7]

I built your tables and set relationships as you show. The subdatasheet correctly displays.

partID and electrodeID should not be in both tables. With the relationship you show, electrodeID should be removed from tblParts

[BDibz]

I built your tables and set relationships as you show. The subdatasheet correctly displays.

You were able to get it to display the subdatasheet with only records with the correct partID? I rebuilt my relationships and still cannot get this to show correctly. Are you sure you didn't do anything differently?

[BDibz]

BDibz,
It would be easier for readers to understand and respond if you could describe the business activity in simple, clear English. We don't know what a Job involves nor how an electrode relates to a part.

Can you tell us about a Job?
What parts are involved?
And where the electrodes fit in this picture?

Sure thing.

A job is similar to an order: it is a request for a certain number of parts. It will have a job number that is the PK, a partID that is the part ordered, and the quantity of parts ordered.
Each part requires certain electrodes in order to be made. One electrode can be used for a certain amount of parts before it needs to be replaced - for this reason I will add a "parts per electrode" column into the inventory table.
The purpose of this database is to maintain an inventory of electrodes; what is currently on hand, and what is the gap between the forecast Jobs and the current inventory.

[June7]

My relationship links show an arrowhead on the infinite side. This means I set a different JOIN type. So changed to remove the arrowhead (INNER join) and the Subdatasheet still correct.

Also, the partID does not show in the subdatasheet. Don't know why it does in yours.

[BDibz]

My relationship links show an arrowhead on the infinite side. This means I set a different JOIN type. So changed to remove the arrowhead (INNER join) and the Subdatasheet still correct.

Also, the partID does not show in the subdatasheet. Don't know why it does in yours.

That was it! Needed to change the join type. Works like a charm, thank you!