I had the idea of providing the user with a list of search symbols in find mode, even when the FM status area is hidden.

For that purpose I added a field "Search Symbols" with a drop-down value list such as:

=

==

!

<

*

etc.

When entering a field in Find Mode, a triggered script memorizes the field name and content. A second trigger acts upon choosing a search symbol in the Search Symbols field, and inserts into the field the user was in prior (including prior content).

This works nicely, except that I get a field validation warning for the Search Symbol field for some symbols. While a * is a valid search criteria on its own, < is not, and FM doesn't like that. The validation warning comes on before the trigger on the field has a chance to act, grab the symbol and clear out the field.

Any tips??

See sample attached

AdvancedSearching.fp7.zip

Some global fields and another layout - but use BROWSE mode to allow entry of the find criteria. Your scripts can then validate the user input before switching to a real find and populating the real fields with the global values.

I believe I understand the work around you are suggesting. I would need a global equivalent to each searchable field in the entire database, and a script which transfers the information to the actual field in find-mode. We're talking about some 450 fields... There must be an easier way?

Sorry, you didn't explain the scope of your problem.

Reading more carefully I can see that you are trying to build a more user friendly interface throughout, but you cannot undermine the need for FM to take priority with respect to validation and it is quite correct for FM to have strict rules in both browse and find mode - what would it do with a find request that it cannot process?

Accordingly these find requests will get processed before any scripts are run - as the scripts may also depend on validated data!

Are you sure you need to search on all 450 fields? Would a subset do it? Have a dedicated find screen with required global fields.