Scripted Find causes drop-down menu to open :S

[Rich S]

Please refer to the attached .pdf of the script I'm using.

Why, when entering Find mode, does the first tabbed field--which also happens to be a drop-down menu--open up? Is there a way of preventing that from happening? I just want to enter Find mode without focusing on any particular field.

TIA for your help,

Rich

Script_screenshot.pdf

[lawaid]

In Form view, it is standard FileMaker behavior to advance to the first element (field or button) in the Tab Order when entering Find Mode.

You could add a "Commit" step in your script after entering Find Mode; however, it can confuse users when no fields are active. What about having your script advance to a specific field, ie, Go to Field?

List view and Table view ignore buttons in the Tab Order. You can customize the tab order in List view and determine the first field to enter for Find Mode. In Table view, though, the Tab Order defaults to the order of fields, from left-to-right, excluding those that don't allow entry.

[Rich S]

Thanks.

Something I didn't think of until I watched a couple of users working in the solution I'm building: one of them entered Find mode, first, before going to the field he wanted to search; the other user clicked in the field first then entered Find mode.

I don't think it makes any difference either way since the end result is the same. Still, a developer might keep that in mind when scripting or troubleshooting a script or function; that might explain why it works when he or she uses it but it doesn't when the user uses it--it could be an order-of-operations issue.