I have a NAME field on a layout that displays a full name that is a concatenation of First, Middle and Last names from a parent table. (Obviously, as a calc field, the data cannot be edited here.)

I have formatted the field as a button so that in Browse mode the user can click it and be taken to the parent record in a different layout. However, I would like the field to be Searchable, so I have enable entry in Find mode.

If the cursor is in a different field on the layout and I enter Find mode, the NAME field is not enterable -- the cursor becomes a 'hand' icon and cannot enter the field (the button doesn't trigger either, since it's a "GTRR" button.

If the user is *outside* any field, the cursor lands within the NAME field and is searchable okay (the NAME field is first in the Tab Order) -- but it would be nice not to have new users run into the problem and have to "learn" a little technique to get around it.

So, is there a typical way of handling this I'm not thinking of? Obviously, I can just put a "Go To" button next to the field instead of making the field a button -- but I kind of like the clean, otherwise intuitive feel of the Field-Button as it is.

Thanks for any suggestions

You could attach the button to a script - and have the script branch according to the current mode. Or use a script trigger instead of a button.

However if you ask me as a user, a button is a button and a field is a field. Having a dedicated layout for Find mode is IMHO the best way to avoid confusion.