Field Script Trigger - odd on Windows

[Tony Hill]

I have a situation where I need to save the current value in a field in case the user cancels the subsequent triggered script on save. I have a trigger on enter and the the save and this works a dream on Mac but fails 4 out of 5 times on Windows. Has anyone else experienced this sort of behaviour? To confirm - it is OK to have two triggers on a field - ie enter & save as I am doing?

[Digital Life]

Tony I have the same experience. On the Mac when you enter the field a script is triggered which stores the current value in a $$Variable. The pop up list appears and everything rests in that state.

In windows the variable is stored, the pop up list appears and then disappears and another script is triggered as though the save/exit state has occurred causing the OnObjectModify trigger to act. Same for OnObjectSave trigger or the OnObjectExit trigger.

Only happens in Windows. If I remove the triggers then the pop list shows and everything rests in that state.