Carl, it will be helpful if you say what it is that you are trying to achieve. Then, some of us will be able to point you in the correct direction.

To answer my question, first i posted the wrong image, which way is best or does it make a difference to create these relationships.

Keep it simple you tend to get errors when trying to do to much and it makes it hard to troubleshoot.  you can always bring to together in another query.

volgen :)

You could use the same junction table for multiple relationships, but it's going to get confusing.

I have multiple Customers, Multiple Contacts, Multiple Ship To
Customers share Contacts and Ship To addresses
Is this the correct way to create the Junction Relationships.

If there is a better way, Please explain

Does your ship-to address table need to be a many-to-many relationship? In other words, do you have different customers who share the same address? Usually, I make that a one-to-many relationship. If another customer happens to have the same address, then so be it. It's just in the database twice.

Yes some customers share the same shipping addresses. I am trying to set up the Cascading combo boxes on my order form. I select a customer then, it then fills in the customer data, then the second combo box lists the ship to addresses associated with that customer and fills in info when selected.
But yes, many customers have many ship to, and many customers share the same ship to with other customers.

OK, then M2M is warranted. You might find it easier to use a separate junction table for it though. What you have there will TECHNICALLY work, but it's going to be more difficult to keep updated.

Thank you  Richard, that is the question I was trying to get answered in the beginning. To use a seperate Junction table

You can get it to work with just a single table, but you're going to find it's more difficult that way. It's kind of like my helper table thing that I set up a while back, where you can use one table to store all of the little bits of information, like a list of name prefixes and suffixes, things of that nature. And you don't want to make separate little tiny tables for all of these. You can do the same thing with Junction tables, but it gets a lot more difficult to manage them all and keep track of what's what inside the table. So, since you typically tend to not have as many many-to-many relationships in a database, I just suggest making those individual tables. You'll save yourself some headache down the line.