m:n table mapping is the way to go

New System Requirement Scenario:

Allow Account Manager(AM) to monitor distributors and dealers sales performance. Distributors shall be assigned specific dealers. These distributors and dealers will be assigned to the AM.

Existing System Scenario:

1. No AM role yet.
2. No relationship between distributor and dealer.

Been thinking of using a classic solution= m:n table mapping. I will have a table called distributor_dealer which has these fields:

1. distributor ID (Primary Key)
2. dealer ID (Primary Key)
3. Account Manager User ID

will code the classes tommorow and test the relationships.