When you define the button, what option do you have set for the current script's action..
Im not 100% sure, just taking a wild guess since I have not tested.. but could it be set to halt any running script ?
Im thinking perhaps the process would go like :
First button click ( run script 2)
Trigger activated ( run script 1)
Second button click (halt script 1 - possibly before it gets to the exit step)
Continue to run script 2 as per buttons instructions.
Actually, in any given case like this, I don't want the field trigger script to halt because the user pressed a button. I want it to keep evalutating the field it's on, until the user gets the data right. It's the button script I want to fail to run if the trigger script sees data in the field that's inapproriate.
Sorry, I may not have worded it correclty...what I meant to say is :
Could it be that your button is currently set to halt the script, if so perhaps due to the speed of clicking, it may be halting the triggered script before it gets to the exit step.
Ah, I understand. No, the button in each case is set to Pause the current script. I also tried Resume, with the same effect.
I may have to do some testing with this myself too... I use this trigger quite a lot.
One more complication to add to this. In the cases noted here, the script triggered Custom Dialog elicited by inappropriate data input offers the user two choices, not just OK. They are asked which of two fields to fix (usually the conflict is between two date fields, A and B, where B must not precede A chronologically). When they make their choice in the Custom Dialog, they are returned to the field they choose, awaiting their dat entry correction. The script trigger does this over and over again until they get it right.
In some cases where I didn't apply my inelegant fix, I found pressing an unrelated button on that layout executed the button script as though the initial script trigger didn't have an Exit [Result: 0} step. In other other cases, pressing an unrelated button on that layout kept placing them back in the Custom Dialog, never leaving them in a field for data correction. All this is resolved with my inelegant solution.