Hi Eric
Take a look at Richard's Video https://www.599cd.com/blog/display-article.asp?ID=1585

You will see  how to create an intermediate table. If you need more help, let me know
John

Hi Eric
If you had a StudentT and a CourseT you would need a 3rd table such as StudentXCourse as the intermediate table. That table would have a numeric field for the StudentId and numeric a field for the CourseID as well as it's own Autonumber field. HTH John

Thank you for the response John. That's one of the videos I mentioned in my OP that I've been watching. My question is how should I go about setting up a relationship with multiple connected many-to-many (m2m) relationships, or many-to-many-to-many if you will. Is it possible to create a "3 way" m2m relationship, or do I set up the relationships as such (using my example in my OP):

I have a ManufacturerT and a VarietyT, so I have the ManufacturerXVarietyT intermediate table, but in our inventory we have different warehouses (WarehouseT) that we pull our inventory from. So to connect the WarehouseT Would I create another intermediate table between the WarehouseT & VarietyT or WarehouseT & the intermediate table ManufacturerXVarietyT or is there a more ideal way about going about it?

Thanks again for your help.

Hi Eric, a more ideal way is when a junction table is an ACTUAL table in your database, and not some extra table you have to make just to make a junction.  For instance, your stock table for the malt can serve as a junction table for connecting your malt and your warehouses:

MaltStockT: MaltID (Primary Key), WarehouseID (PK), StockQty, OnOrderQty.  
(Note: Stock is actual on-hand stock, and "on order" quantity is the ordered quantity that hasn't arrived the warehouse.  I once worked in retail and manufacturing too, and sometimes we ordered items weeks/months in advance, so we had to keep track of what was "on order."  And this number should be put here, right next to the stock.)

You can create an order table for storing your orders you place to manufacturers, and that will serve as a "junction" for connecting malt and manufacturers.  An "order header" contains info for an entire order, and "order detail" contains multiple items for that order.  E.g. you order multiple malt items from one manufacturer in one order:

OrderHeaderT: OrderID (Primary Key), OrderDate, ManufacturerID, ArrivalDate.
OrderDetailT: OrderID (PK), LineNum (PK), MaltID, Quantity, UnitPrice.

Thanks Kevin.

With your explanation and also talking through it with one of my collogues at work, I think I have a better understating of how to set up my relationships now. I was definitely making it hard for myself, with having certain fields in the wrong tables and just having too many unnecessary tables.

One more question Kevin. This is how I currently have my relations set up. Would this the ideal way to set it up?

You can ignore some of the duplicate fields, It helps me visualize were the ID data is related instead of just looking at ID numbers.

Hi Eric, what if you order the same item from two different manufacturers?  Then you'll have two different values for ManufacturerXProductID in the InventoryT table for the same item, two different stocks for the same item, two different everything for the same item, etc.  Is that what you want?  That depends on your business.  I would have to know more about your business to know if this setup is useful or not.  Also, you don't necessarily need to join all tables together.  Only do it when you need to.  The picture below is how I did it in my old job.  Normally, you use the relationship diagram only if there are relationships you want to "enforce."  But not all need to be.