Out of curiosity, what happens if you follow the Go To Related Records step with a Go to Record/Request/Page [next] step?
Does that make for a possible work around?
Thanks PhilModjunk for the suggesstion. I tried that (again) and it didn't solve the problem. I have tried all sorts of workarounds, but it appears the double-click interrupts the process sufficienty that the script is ignored at some point. Somewhere in the process, Filemaker IWP decides to display a certain record, and it simply does that, regardless of how you try to circumvent it.
Have you worked with IWP to the point that you've been able to resolve this with your own solutions? I'd sure like to find a workaround that is rock solid. I don't think I've committed any basic errors, been working with Filemaker since it was owned by Nashoba...
Filemaker engineering doesn't appear to be interested in this, but for me it is extremely important, due to the sensitivity of the data. I would hope they would see it the same way, as it shows some fundamental issues with their programming. There is another issue that is tied to this. Even if you do end up on the right record, using the Back button on the browser will also take you to an unrelated record. I got around this partially by forcing the server to log them in a url that kills the status area of the browser itself. But now I'm finding that with some mice, like the Apple Magic Mouse, you can swipe left and it does the Back function. So that overrides my workaround.
Frustrating to say the least.
Filemaker, where are you?