There is more than one way to script a find and I can't tell what method you are using from your example, but if you pattern your scripted finds after the example found here: Scripted Find Examples
You would use:
Enter Find Mode 
Set Field [YourTable::Job_Title ; "=Councillor*" ]
Set Field [YourTable::Job_Title ; "=Leader*" ]
Set Error Capture [on]
Perform Find 
ah god this thing is driving me nuts.
i'm in 'filter portal records'.
i am entering a statement into calculation window that looks like this:
Contact_Data::CS_Job_Title ≠ "Councillor*" and Contact_Data::CS_Job_Title ≠ "Mayor*"
the desired effect of which is to eliminate all jobs with 'councillor' and 'mayor' in the job titles and returning everything else.
is there just a simple statement i can chuck at this?
You cannot use wild cards in portal filter expressions. They can be used only when performing finds, constraining or extending found sets.
Left ( Contact_Data::CS_Job_Title ; 10 ) ≠ "Councillor" and Left ( Contact_Data::CS_Job_Title ; 5 ) ≠ "Mayor"
I don't suppose there is a code that can simply identify when those terms arise in a string? ie - eliminate Deputy Mayor not just Mayor?
What I posted exactly matches how the * the wild card would work if it could be used in a portal filter. If you want to replicate the logic of using *Mayor* instead of mayor*, use the PatternCount function.
thanks for that.
You might find the following FileMaker Free to Download file of interest:
It demonstrates many different methods for selecting values when a simple or conditional value list alone can't quite cut it. It includes some auto-filtering search portals where you type text into a search field and the records in the portal "filter down" with each keystroke. One option is the "starts with" approach of my original response and the other uses PatternCount to do a "contains this text" type of filtering.
very kind, excellent resource. thank you.