if by volume you are speaking of the number of rows, I would have few suggestions implement the Partyrelationship so it pulls less records (Iknow it is a database specific). allow the customer to select which fields they see and default queries. with the default queries, you can shrink the find windows.
have a wrap format for output that fit the screen width they are using. Hans Bakker sent the following on 9/20/2011 1:37 AM: > I know this has come up before and every once in a while a customer is > asking how the reduce the display volume of the back-end. > > How about change the screen, form and menu renderer to check for every > field in a database if it should be displayed or not. > > The system should be able to start in config or normal mode. Config mode > will enable the user the click on check boxes next to each field or > menuitem on a screen if the fields and menu items should be displayed or > not. > > the result is stored in an entity which is interrogated when the system > is in normal mode. > > > any thoughts? > > > Regards, > Hans >
