How many fields are in the related table (not the layout, but the table itself)?
The table has 17 fields.
The layout displays 6 fields.
Some of them have a value list.
One of them has condicional formating.
Well, that certainly doesn't sound excessive. How does it behave on a local machine (that is, when it's not being hosted by Server)?
On a local machine, it goes really fast.
Hello again, Javier. Sorry for not having gotten back sooner.
That makes it sound like a network / bandwidth or server performance issue, all right. Check a few things:
1) Do you have any large fields (i.e., lots of text, containers, etc.) that are in those related records? I know you didn't have any on the layout, but what about in the records themselves?
2) What about any calculation fields - any summary fields, unstored calculations, etc., on the layout where you're heading?
3) How many table occurrences are on the graph? If it starts to get really busy, you can suffer a performance hit because of caching.
4) Is this a list view, table view, or form view? How many records fit on the screen at a time?
5) Are any of your fields based on pulling a value list, especially a related value list?
6) Check your server stats. What is your cache hit %? (Should be close to 100%.) What is the client I/O time and time/sec? If either of these is high, increase the cache size in the server settings. Also, check the network traffic; if the bytes is high, you may have a lot of traffic going back and forth, which indicates a drag from bandwidth.
Those are just some ideas off the top of my head. If none of that happens to hit a speed bump, we might have to dig deeper.
Instead of a GTRR, why not just a simple scripted find?
Thanks, David and Mike for you suggestions.
Give me a few hours to try all of them.
Javier Durá wrote:
A global field stores current date.
I use the "Go to related records" script step to show only today, future or past events using 3 different auto-relationship:
Do you have any idea of how can I improve the speed in this solution?
Are you perhaps using the "Show only related records; Match found set" option in the Go to Related Record step instead of "Show only related records" (match current only)?