First Timer: Product Inventory Table

Alright! This is great. 

I now have my Products table with ProductId(PK), ProductName, and SupplierID. and I have my Suppliers table. I am reading about junction tables and it says 'it's a special table that keeps track of related record in two other tables". I am assuming that the "other two tables" would not mean my Suppliers and Product table, but the Product table and another table. Am I assuming correctly? If so which table would I put my second SupplierID field?

I agree with Ken because you can't show such a situation without the junction table. So even if it occurs rarely, if it occurs and you aren't using a junction table, it will be impossible to create the relationship unless you lose the record of the other Supplier.

With this being a rare occasion would it still be benefical to have that many-to-many relationship?

Absolutely.  You don't lose anything by it and you can cater for those rare occasions as and when they happen.  In fact, it may seem strange, but there are even occasions when a simple one-to-many relationship type is modelled by a table in this way, and is recommended by Chris Date for those situations.  The reason for doing so is that it avoids having a Null foreign key where a row in a referencing table does not need to reference a row in a referenced table.  In some situations a Null foreign key can be problematical as Null is semantically ambiguous, having no fixed meaning.  The best you can say is that it means something like 'maybe'.

I understand. I am asking myself that question but I don't seem have a either yes/no answer. I usually stick to the same supplier for reorders, unless I decide to order the same product from a different supplier due to personal or business reasons. This happens rarely, but it does occur. With this being a rare occasion would it still be benefical to have that many-to-many relationship?

SO then I shouldn't have it as a foreign key in the product column? What exactly are you saying I should do with the supplierID? Keep in mind I still have a SuppliersID table that lists all the suppliers I use.

As Scott says, it all depends on how you source the products.  I make the point in the light of my own experience.  As it happens, early in my career I worked in the Purchase and Supply department of a manufacturing company, and it would have been unthinkable not to have an alternative source of supply for any item as, if that source failed for any reason, we would have been in trouble.  In our case the range of items bought was extensive, the biggest categories being packaging materials and engineering components, so we were not buying manufactured products for distribution (the raw material for the product was actually purchased at source in other countries).  Your business model may well differ in that there can only be one supplier per product, in which case you'd simply need a foreign key SupplierID column in Products.  You know the reality of the business model, we don't, so only you can determine which is the appropriate database model.