Try this type of setup for your Table Occurrences and Relationships to see if it meets your needs:
The Client_Part table is a join table that holds one record for each combination of Clientele and Inventory Part sold. It provides a way to handle a many-to-many relationship between your clients and parts. The Payments can then be associated to each combination of Clientele and Inventory Part allowing for multiple payments of varying amounts. Base your layout on Client_Part with a portal to Payments.
I was kind of confused with what you wrote so I am attaching the basic phase of my database. The problem is, I want to see all the payments under the specific Inventory_ID as a list just like a portal, but in my case they are all seen as different records even though the Inventory_ID is the same. (I chose unique value under validation but to show you my point, I cancelled).
In the next step, if I can show different payments under the unique Inventory_ID, I will use this on another database as a portal which summarizes the whole project.
Thanks in advance.
I can not see any attachment in your last post.
Does your Inventory_ID (that I called Part_ID) identify one specific and unique part or does it identify several parts that have identical specifications? If it is the later, then you will probably need a join table as I illustrated because, in this case, one client can buy many different parts and one part can be sold to many different clients.
You may still be able to list all Payment records for a given Inventory_ID since they are related through the Client_Part Table.
i got it! Thanks!