I would replace the global variable that you set with a global field added to the portfolio table. In a multiuser environment globals fields have their own unique value per user. Make the value of the global field equal to the value of the primary key for the records that the user has been assigned. Now you can create a related table occurance to the records for that portfolio using the global field of the parent equal the primary key of the child. On your layout you can now show all the related records using a portal. The beauty of doing this over performing a find is tat the records will show dynamically as records are added to or removed from the portfolio.
Do they ever need to change the found set (ie find a subset of the total records available to them)? If not, you can do your Find on open and then take away the ability to change the found set (take off Find, Omit, Show All, etc). Or you can set security privileges which will restrict their found set regardless if they can search or not.
I would replace the global variable that you set with a global field added to the portfolio table.
I created a global field and set it using the variable I had created. I know I could have killed that part and instead of the variable just set the field but it was quick and easy.
Now you can create a related table occurance to the records for that portfolio using the global field of the parent equal the primary key of the child.
On your layout you can now show all the related records using a portal.
In the Portfolio table there will only be one record for the portfolio. And I can't show the trouble ticket records via a portal because I have to show RMA and defect records in portals in the trouble ticket records. I saw a doc online about using self joins as the best way to limit record views but I lost it. From what I remember it sounded a lot like what you are trying to stear me to do. I just haven't wrapped my head around it yet.
They will need to be able to find open records or closed records. I thought about what you suggested with some preset find scripts.
Seems like this is what I need and what Johnners was trying to explain. If I use the portfolio as the relationship does that mean that every record has to have the portfolio number? I ask because they all have a contract number which is related to the portfolio number.