We’ve mentioned this since the release of FMS v16, but it looks as if we’re going to have to reengineer many of our systems that use the Go to Related Records script step.
I’ve just had to replace a single line of GTRR on a button with a script that comprises of about 22 lines once error capture, comments, etc. are included.
GTRR was such a staple element of our development since FileMaker became a relational database, but over the last 3 years, it is going to have to be retired, as (in Windows) we’re constantly getting ‘Not Responding’ appearing when using it, whereas entering find mode, go to layout, set field, perform find works instantly.
I have no idea what they’ve done to the database engine, but in today’s case the relationship was one hop away without any further links and had 2 conditions in the field match, hardly complex.
I’ve previously reported upgrading a client from v14 to v17 who had a brand new well specified server, we’d converted all layouts to themes and styles and all PCs were replaced with new ones and the server was connected via Gigabit Ethernet via an HP Procurve switch (great backplane on these). Within a day, they were complaining the database was running too slow. Again mostly the GTRR original script steps being the culprit. We have many, many more examples.
I’d be interested to hear other views on this, but our recommendation is now keep clear of Go to Related Record in your solutions.