Here's a workaround you can use:
If [Not $$TriggersOff]
Set Variable [$$TriggersOff ; value: True]
Put your current script here
Set Variable [$$TriggersOff ; Value ; false]
This is a method you can use in any situation where you need to keep a trigger controlled script from tripping its own trigger.
Thank you for your response.
Unfortunately, this is not the problem. I'm aware of the technique you describe. The problem isn't that my trigger-controller script is triggering itself. It's simply that I return to the object that triggered the script by issuing the Go to Object script step.
Going to an object is not the same thing as pressing a key, so there should be no reason for FileMaker to infinitely trigger the OnObjectKeystroke trigger.
Your proposed solution does not work.
This is definitely a bug.
Again, thank you.
I cannot reproduce the bug.
Using Windows XP, I created a one line script:
Go to Object ["field1"]
I gave a field on the layout "field1" as its object name.
Set up field1 with the OnObjectkeystroke trigger
Watched trigger perform script in script debugger and also tested with debugger not active.
No infinite loop occurred.