Is there a way to disable Enter Key?

If my users hit the Enter Key rather than the "Perform Find" button, undesired results follow: rather than switch Layouts, they stay in the "Find" Layout in the Browse mode where they are able to modify data.

No, but you can put them in a script and pause it, then format your Perform Find button to merely Resume the script, which can either call your Perform Find sub-script or contain the remainder of your steps. Then pressing Enter or clicking the button will perform the same function.

The script is started and then paused.

If user hits Enter Key once, cool

If user hits Enter Key again, we're back to same problem.

Hm... Perhaps you could do something like this:

Enter Find Mode

Loop

Pause Script

End Loop

Then make another script with the rest of the steps, and attach this to the button?

If your script has no more pauses, then it should not matter whether or not a user presses Enter twice. The script should perform the find and go to the desired layout, once it is resumed.

-Queue-

Good point, great solution, thank you!, it works....

but...

there are other script buttons on the layout, and they are unable to be performed since another script is paused.

I suppose I could move those script buttons to another page....

Buttons can be programmed to Exit/Halt a script in progress.

hmmmm.......

Mark:

You should consider building more layouts, and sending the user to a layout where it is clear what they can and can not do (i.e., if they're in the middle of a find, don't have loads of buttons sitting there which are effectively useless) and then return the user to a more suitable layout at the end of the function.

It might seem to be a headache for you now, but it's better than the endless headache of having to deal with confused and angry users later...

-Stanley

That worked! Problem solved. Thanks to you both!

Thanks for input Stanley, we have a good solution to the issue.

The Enter Key is effectively running the scripts I want

and the other Script Buttons halt the "paused script" and run as they should.

I'm very happy. Thanks again all.

If I could, I'd like to add my 2 cents worth.

Within all my "find" type scripts I construct something like the following:

If ["Status(CurrentMode)=1"]

Perform Find [Replace Found Set]

Else

Enter Find Mode [Pause]

Perform Find[Replace Found Set]

Endif

I think that this approach works best (for me) I can provide my users complete functionality, without them even knowing that they are within script controil.

Alan Barker