Because my search windows do not display the toolbar, users have no access to the search operators. So I have placed them in a drop down list on a text field (in the footer) with a button/script that places the displayed operator wherever the I-beam is flashing. This works fine for most operators, but whenever I choose one of < > ≤ ≥ , I get "This field contains invalid find criteria. Allow this invalid value?". Although I can click "Yes" and the transfer works, it is then not accepted by date and number fields (I get the "Modify Find" dialogue box).

Can anyone explain why I am getting these error messages with these 4 operators? And why Date and Number fields would be rejecting their use? (just in case it's not obvious, they also reject <= =>)

Hi Wikisnoodle,

Are your operators global fields? If not, they won't be found in Find Mode to use in your finds. Also, you show 11 Advanced, what shows when you walk it through debugger? What is placed into the field at that moment? If possible, please provide your script. :-)

Thanks for taking an interest.

The operators are accessed via a drop down value list (no script), on a non-global text field located in the footer (a global field will not display a drop down list in this location).

Whatever the operator chosen from the list, it appears in the text field (only < > ≤ ≥ throw up the error message and require a 'Yes' to continue). Next, the user clicks where they want the operator and then clicks a button to transfer the contents of the text field to that location. The transfer script works fine.

Just those 4 operators throw up the error message when 'dropping' into the text field and the same 4 refuse to work in date and number fields when performing a find.

Why don't you post a file (preferably a simple one) showing the problem?

Attaching simplified file. Although there's 2 tables/layouts, It all happens in 'List' / Find mode.

Operator Problem.fp7.zip

Yes, this is a problem. Ideally, the Choose Operator field should be global - but Filemaker will not let you enter a global field in Find mode (I am not sure exactly why not). OTOH, if the field is not global, then > alone is not a valid entry in Find mode - and I don't see a way to skip this validation.

Thanks for your time. I suppose I can get rid of the second warning by getting the users to fill in their criteria first. I don't know of a way of getting rid of the first, irrelevant error message.

I don't really have a good solution. Perhaps a hack: instead of inserting ">" into the field, insert "> [tab] greater than" and place the tab position beyond the field's right boundary.

Thanks for the suggestion. I can see that working. :-)