I think if you were to add a show custom dialog at the start of your triggered script, (as a test to see when the script is first performed), you'd find that this script trigger doesn't "fire" until you exit the field.
Until you exit the field, there is no way for filemaker to know that the user has finished editing the field (since you can edit dropdown lists by typing in the field--even after you've selected a value).
I'm sorry, that is not what is going on.
Best is to use Script Debugger, which shows that the script is triggered and does what it should.
But then the drop-down drops again.
I can mail a file if you want.
Sorry, I missed the "A" or I wouldn't have suggested the show custom dialog.
I suspect you may have a damaged layout as go to field works pretty reliably of myself and others. I have seen cases where it failed due to layout corruption. Try placing this field and script trigger on a new layout and test it. Do not copy any layout text from the problem layout.
No, I reproduced it by making a new simple database file, which if you like I can e-mail if you send me your address.
But I repeat: It works ok when Tab Order is activated for the fields, however I find it no good as it selects the next object in the Tab order.
I want to control it by the trigger script (which triggers ok).
What is wrong is that after script step Go to Field (which it does ok), selection returns to the filed with the drop-down list!
I regard this as a bug issue.
OK, I spotted the issue when I attempted to recreate this. The ObjectSave event precedes ObjectExit--which kicks in the next field action that determines where to place the cursor. Your script correctly places the cursor in the specified field, but once the script ends, the ObjectExit event kicks in and relocates the cursor--and this leaves the cursor where you don't want it.
The fix, is to add Exit Script [Result: False] at the end of your script. Exit Script with the False result cancels the event that triggered the script for many script triggers. (You can read more about this in the help system.)
Apologies for not spotting the real issue sooner.
Thanks, apology accepted! That was a piece of information I had missed.