I have a solution that uses many portals (and therefore many realtionships) showing related data from another single related table.
All the portals are displayed on the one layout.
At the moment, I am using multiple relationships, each portal displays values from the one related table using globals. The globals change on a fairly regular basis. (it's a little bit like a 'console' application). Changing one global usually changes all the other globals, therefore, everything else from the related table changes, giving a summary of all sorts of info.
I was thinking that it might prove to be better performance if I change the many relationships to a single relationship and simply use 'filters' on the portal (using the same globals) to show the related info I need.
But, before I make the change, I wanted to know if there would be any performance benefit? The solution is on a WAN and it can be slow displaying multiple portals to the one table on the one layout.
Anyone have any ideas about this?