Hi @Christa_Patton1,

It’s a little tough to tell from your description what exactly your end goal is, but I can tell that you seem to be thinking of your Airtable base in terms of a spreadsheet.

Since I can’t quite decipher what your end goal is, it’s tough to give specific advice, but I will give this general advice, that you might want to consider structuring your Airtable base more like a database (which is Airtable’s intended purpose).

Rule #1 of databases is to keep all similar “things” in a table together, not spread across multiple tables. You have 7 vendors, you said, and are keeping a table for each one. They are all vendors, so they should all be together in a “Vendors” table.

Another rule is to use relationships to establish shared stake in a “thing” across multiple entities, rather than creating multiple copies of “thing”. You offer “Products”, and one or more of your “Vendors” may supply that “Product”. All the “Products” should live in one table, and a relationship established between a “Product” and a “Vendor” that supplies it.

Here’s a real quick example base for you that I think might start to get you moving in the direction you are wanting to go:

Take a look and ask more questions, and maybe we can home in on how to make this work for your use case.

To establish a relationship between a product you offer (from the “My Products” table) and a vendor you buy from (from the “Vendors” table), you can create a “Vendor-Products” record. You can do this from within the “My Products” table by clicking in the Vendors linked field:

and selecting to create a new record:

You’ll see that the “Product” link is already made for you (the product from which you clicked in the Vendors field. You can then select a “Vendor” that carries this “Product”, and list what special name that Vendor gives to this product, as well as that vendor’s price:

Keeping records in this way will reap you many benefits, such as being able to average prices across vendors, or find high/low prices among vendors.

You can view all the “Products” from the perspective of a particular “Vendor” from this “Vendor-Products” table by creating a View that filters to show only that “Vendor”.

Hi @Jeremy_Oglesby,

Thank you very much! I think this will get me moving in the right direction. This might just be the reason I was having trouble. My relationships and thought processes were more like a spreadsheet rather than a data base. Even though a data base is my goal. While I might not have been able to articulate exactly what I needed I think you did a great job tracking it and giving some insight. I’ll circle back if I run into any more snags as I learn the ropes. Plenty of information to put into action. Thank you