How to incorporate other tables into a "Related Whatever..." view to use Historical data

[pkunzipula]

Hello Appsheeters.

I've been stuck on this one for over a week.

I'm creating a Field Inspection app. User creates and saves Company. Then they create and save a Report attached to that company. Then they create and save Items attached to that Company (not the Report, in my current version).

Upon 1st visit, Company has no Items. Inspector creates all new Items.

On Future visits, Inspector should be able to see all currently Active items belonging to that Company, then add them to a new Report and/or create new Items.

I created a quick demo of my proposed workflow (this demo shows Items_Inline filtered by CompanyID, toggling a single column). This approach creates a host of future problems when the same items show up across multiple reports. 

I also tried working directly with the Related Items view to keep the relations cleaner, which would be ideal if every New Report only had New Items. But I need a quick way to access the Company's past Items as well.

Has anyone created something similar? Can you advise me on how I should approach this? 

I thank you for your time and expertise!

[Steve]

I'm confused about what you need help with, but to address the title of the post: a single aggregate view (table, deck, etc.) can only include data from one table or slice.