Set Variable [$currentObject; Value:Get( ActiveLayoutObjectName )]
Set Variable [$query; Value:Get( TABLE::g_search_field )]
Commit Records/Requests [ ]
Perform Quick Find [$query]
Go to Object [Object name: $currentObject]

*fileds can included in the Quick Find by selecting the checkbox in the new Inspector / Data tab / Behavior section.

robear

I’ve called the first one: TextToList (String ; Numeric )

Let ( [

Counter = Length ( GetValue ( String ; 1 ) ) ;

NewCounter = Numeric ;

NewList = String & “¶” & Left ( GetValue ( String ; 1 ) ; NewCounter ) ;

NewCounter = NewCounter+1 ] ;

If ( NewCounter 1 ; TextToList ( MiddleWords ( String ; NewCounter ; 1 ) ; 1 ) ; “” ) ;

NewCounter = NewCounter+1 ] ;

If ( NewCounter ? Counter ; TextWordToList ( String ; NewCounter ; NewList ); NewList ) )

Once again, you’ll need to call this with a Numeric value of 1 and also a StringList value of “”.

Finally you’ll need to create a calc field in the portal table that has the following:

TextWordToList ( SearchField ; 1 ; “” ) & “¶” & TextToList ( SearchField ; 1 )

SearchField should be the field that you’re try to search on (eg a full name field).

This calls the two functions in a useful way and will convert the string Tom Thumb into :

Thumb
T
Th
Thu
Thum
Tom Thumb
T
To
Tom
Tom
Tom T
Tom Th
Tom Thu
Tom Thum

By calling the functions in the way described, the first word doesn’t get repeated which saves on some disk space / filtering speed with larger databases. From this list you can search on the words Tom, Thumb, Tom Thumb, Thu, etc and get a positive result. Combine this with the OnObjectModify script trigger and you’ve got a rapid portal filter that will search on any word not just the first one.

Note : There are a couple of spurious carriage returns at the start of the calc field but I only had a short while to run through it and have only just noticed their presence – they’re easy enough to remove though : )

I adjust it mildly, cos i use mine as search fields and am not always editing the last letter, but also previous words:

Set Variable [$currentObject; Get ( ActiveLayoutObjectName )]
Set Variable [$currentSelectionStart; Get ( ActiveSelectionStart )]
Commit Records/Requests []
Go to Object [ $currentObject ]
Set Selection [ Start: $currentSelectionStart ]

This means that wherever you edit in the field you are sent back to relevant position. To be sure a minor adjustment!

Blessings, T

- Dave

Let( [

secondWord = MiddleWords ( Name ; 2 ; 1 ) ;
thirdWord = MiddleWords ( Name ; 3 ; 1 ) ] ;

ExplodeToMultikey ( Name )

& Case( not IsEmpty( secondWord ) ; ExplodeToMultikey ( secondWord ) )

& Case( not IsEmpty( thirdWord ) ; ExplodeToMultikey ( thirdWord ) )

)

@Indra: you shouldn’t have to refresh the index. Modifying an expression in a stored calculation field will automatically force the host to reevaluate the field and it’s index.

- Dave

However – just tried Indra’s mod to make it list for any word in the field. But it works just the same!

I have followed the instructions, carefully, copied out the line of text to modify the function and refreshed the indexing as specified. – no change.
The index field lists as the example below – is this correct? (surely it should just list the words individually)?

F
Fo
For
Ford

F
Fo
For
Ford
Ford
Ford M
Ford Mo
Ford Mot
etc …

I had just finished implementing it when I stumbled upon the recent “Ergonomic Stimulus Contest” run by Albert Harum-Alvarez of Small Company. So I submitted an entry and won 2nd place! Your technique is a winner! I gave you guys credit for the technique in my entry and presentation. Thanks again.

A client wants me to re-design a twenty-five year old database app. They do heads-down data entry and this “spotlight filter” functionality is one of the most important things to her. Without it, I wouldn’t get the job. I’m just learning to use FMP and was discouraged to learn that I would have to re-invent the wheel.

Thanks to David Graham for saving everybody a great deal of time and money. It’s an elegant solution.