I'm creating a new database for our company. We have elected to begin with the FM Starting Point. It has most of the elements we need, however, one very important aspect of our business needs to be added.

We are a vendor to the property management industry. Therefore, we have property management accounts and property accounts. Both are account records. We need the ability to relate the property account to the management account. A simple parent child self join should work for this. Add a portal and we can see all the property accounts that the management company has. However, we also need the ability to carry this relationship through the rest of the tables.

We would like to see all the estimates, projects, invoices, etc of the child accounts (properties) on the parent account (management) portals. As well, we need the ability to list management account contacts to property accounts and carry that relationship through to the other tables as well.

What is the best structure and methods to hook everything up that keeps excellent performance? Is a parent child/self join the best method? I really appreciate your help.

Update: Would it be possible to add a foreign key on the project, invoice, etc tables with an id_management_account. That would allow two accounts to be linked to the same project. On the account, create a new management layout with portals set to display projects with the account added to the management account field. 

Could we use a script trigger to determine which account layout to load? if account is type: management account it will load the new layout?  How would this effect interface performance? 

Other ideas? 

My recommendation is to contact them directly and have them make the modifications.  

The solution is very detailed and complicated and they obviously know it thru and thru.

Spending a few bucks with them to modify it would be money well spent.