I have a layout that displays results in a portal from a value list. The value list field is a global that is related to another table...that's how I'm displaying the results in the portal. I've noticed that the browser is incredibly slow to update the related fields in the portal after a user selects a value in the global. My cpu usage on the server (Xserve, second gen, 768MB RAM) shoots way up and it appears to be the fmweb process doing it. I'm using Server Advanced 8.02.

Anyone have ideas' about what's going on? I've tried optimizing everything I can on the server and database side.

Scrollbars is it probably, fixed length portals in a tabbed layout makes you while switching from tab to tab change the key value in smaller chuncks, to make it hog less power.

When it comes to it no one except people with ausperges syndrome grasping whole pages in one blow, structuring the output eases the burden for both machinery and reader.

--sd