Tab order & GoToField misunderstanding?

[LaRetta]

On another forum, a question was posed: http://forums.filema...cd768309#173535

OnObjectExit trigger - The only way I could make it work is to end the script with Halt Script. This struck me as strange because when a script ends, it halts anyway and we never need to end a script with Halt Script.

Debugger shows it does go to the specified field but then immediately jumps to the next in tab order. I did not expect this behavior (between tabs and script trigger) and I am trying to understand the underlying logic:

• User tabs which exits field
  
• trigger fires and places cursor in field outside of tab order
  
• tab attempts to finish after script ends by moving to next field in tab order
  

If FM is holding this 'I must finish by moving to next field in tab order after this script ends', might this not bite us in other script triggers, particularly (but not limited to) triggers which move through fields or that depend upon landing in a specific field?

Input greatly appreciated. To make it easier, here is sample file.

Trigger.zip

[comment]

The OnObjectExit trigger runs a script when an attempt is made to exit the active object. If the script returns true, the original event proceeds normally - after the script has run. The 'original event' in this case is tabbing out of the field into the next field in tab order.

Since the script has already moved the cursor to another field, and the OP does not want the 'original event' to proceed, they should end the script with Exit Script [ False ]. It seems like halting the script achieves the same thing - but it also has wider repercussions than that, so I don't think it's a good replacement.

Note that not all script triggers run before the 'original event' is executed.

[LaRetta]

Hello Michael!

Oh of course! The original event is the tab! Now that you explain (as only you can), it makes perfect sense. I have notified the OP of your better solution. Thank you. :laugh2: