How do I block a user to perform a find by hitting the enter key? I want them to only use the buttons for adding another find request, cancel, and perform find. I dont want the user to be able to hit enter and perform the find because I use s different layout for finds. If the user hits enter they would get the results on the wrong layout.

I have tried to hide and lockout the status area but that did not stop the user from performing the find when they hit enter.

I suppose you could put them into an endless loop and have it escape only by hitting a button--but what's the point? Why not allow typing enter to continue with the Find? I should think this would be a desired feature. :qwery:

To elaborate a little, put a Pause in the initial script, followed by the remainder of the steps to be performed after the find (or a call to the steps in another script) and set the Perform Find button to merely Resume Script, so that it performs the same action as pressing Enter.

Johnny:

If you're creating deeply scripted finds, you may want to have the user enter the requests into globals in browse mode, then create the find from the globals in a script, triggered by a button.

-Stanley

If, in Field Behavior, you check 'Go To Next Field using' Tab AND Return, then hitting Return will NOT activate a Find. At least that's how it works on Windows.

Now ... Enter and Return aren't the same thing, I hear. But if you mean the standard means of activating a find (via RETURN), this will stop them.

BTW, this is good and bad. I click [Return] on many fields to stop carriage returns and move users to next field. But it ends up biting me for the very reason indicated ... it won't then trigger a Find. It seems we can't have it both ways ...

In truth, the Browse/Find and Tab/Enter selections should be a 4-way possibility. Alas, it is not; one can't specify that, only in Browse, have Return move to another field but if in Find, have only the TAB move a user (thus firing the Find) when Return is hit.

Ah. ENTER will still fire Find. But if all three are checked (Tab, Return AND Enter), it won't fire no matter what they do!!

L

Thank you all for your input.

Ender: This is what they required in the specs that were given to me. They do not want the Return key to be able to perform the actual find.

Queue: I have implemented your method. Thank you.

Stanley: I am curious on how this would work for adding new requests though. If you use global fields, would you have to perform a find each time and then expand the found set every time the user would hit the button for adding an additional request? If this is true then if the user hits the cancel button, the original found set would no longer be there.

Laretta: Thank you for your suggestion and input.