I think the delay is due to having a list view layout with a great many filtered portals. If you can modify your design to eliminate the portal filters, the screen may update more quickly. In most cases, the "filter logic" used to control which records appear in a filtered portal can be replicated at the relationship level and this should speed up your screen refresh.
Also be aware that relationships that use inequalities will result in slower updates and there may be ways to modify such relationships to eliminate them.
Also, if you are using Refresh Window [Flush Cached Join Results] to update the screen. Remove this step. There are alternative methods for updating filtered portals after modifying a field referenced in the portal filters.
Thank you for the hints. I will try to modify the design to avoid filterd portals.
Just for curiousity what the alternate methods to update filtered portals.. can you refer to some articles or tell me about it if it is short.
Say you have this relationship:
LayoutTable::PrimaryKey = PortalTable::ForeignKey
You put a portal with this portal filter expression on your layout:
PortalTable::Category = "Apple"
You now have a portal that shows all related records, but only those where category = "apple".
Add a calculation field to LayoutTable, constApple that produces the text: "Apple"
To remove the portal filter, you can now use:
LayoutTable::PrimaryKey = PortalTable::ForeignKey AND
LayoutTable::constApple = PortalTable::Category
And the new field need not be a calculation field like it was in this example, it can be a normal data field that is assigned a value by a script.
The downside to this approach is that you may need to add a very large number of additional Tutorial: What are Table Occurrences? that refer to PortalTable to your relationship graph in order to replace the use of portal filters.
If I understand you correctly this is what I will do
I have up to 13 columns in the booking screen
so I will create 13 additional calculation fields in the layout table and populate them using a script with the names of the teachers I need to display
then I will create 13 table occurances for the portals and relate each one to a calculation fields (in addition to the exxisting relation)
I hope this will result in a considerable time cut, I will let you know the outcome when I finish it.
You might consider using 13 text fields instead of calculation fields for the teacher names. That will make it easier to change names when you experience a turnover in your teaching staff.
I forgot to mention that once you have the portal filters gone, you can also completely remove the portals and just keep the fields--which should be respecified to refer to the newly added table occurrences.
Ok thank you