@Christa_Patton,
It sounds like what you need is a “join table”; another table that sits between your “Property” table and your “Inventory” table. I’m not sure what an appropriate name might be… perhaps “Property Inventory”. This table will contain “line items” that represent a unique inventory for a client/property.
This new table will contain one record(row) for each instance of a piece of “inventory” being used at a “property”. Each record(row) will have a linked field linking it to the Property it will belong to, and then to an item from Inventory. You probably don’t want to link multiple items from inventory to a single line item (record) in this table. Each record will be linked to ONE property and ONE item from inventory. In this way, you can reuse the same items from your Master Inventory list, but still have individual instances of that item’s use across multiple properties.
In addition to those links, this table could contain fields for any data that are relevant to the use of an inventory item in a property, but may not be relevant to an inventory item on its own (such as, perhaps, “Date Ordered”, “Date Arrived”, “Price Obtained For”, “Room Placement” – I don’t know your application, just shooting from the hip here…).
This will enable you to “Group” or “Filter” this new join table by “Property” – and once grouped this way, each grouping or filtered view will represent the unique inventory for that property, as assembled from the Master Inventory list.
Hope I wrote that all in a way that is digestible and applicable for you :slightly_smiling_face:
