This often happens when users confuse the browse mode for the find mode. Sometimes a simple user interface change like the background color turns slightly different when in Find Mode would work. Or you can do other things like have a toggle to Edit so that in browse mode you can only Edit if the Edit button has been turned on.
do you have FMP Advanced? If so, you can create a custom menu that either prevents finding altogether (unless you add a button for it), or makes ctrl-f fire a script where you can have better control over what the user does.
I have seen the same issue for years and this is an inherent problem if you allow the same two tasks on the same layout.
One way to separate the two is to set up a group of global fields to be used for entering search criteria while in browse mode. A script then enters find mode and uses the global field data to set up one ore more requests and performs the find.
These globals can be placed inside a popover or in another layout used with a new window step to provide a dialog window.
As David mentioned, a custom menu can make it so that trying to enter find mode opens this window or popover. (A button located with these fields performs the find script. )
I've done what the above comments have suggested. However sometimes I don't want to spend the time to add more complexity, so I'll do this down and dirty way. I just add an OnObjectEnter script trigger to the field that basically does a check of "not isempty (field)" then "Show custom dialog" saying something like "Are you sure you want to change the contents of this field".
1 of 1 people found this helpful
watch out for popup/alert/alarm fatigue