Speed
Why is Search Results So Fast?
Matt = Genius
fmSearchResults can be incredibly fast-- Matt demoed this technique at DevCon against databases with millions of records and it was nearly instant. But then again, so is FileMaker. That is the key here: this technique lets you make sure that you're always searching the fastest way FileMaker can search: searching on indexed fields in the same table as the layout you're searching on (this all goes on behind the scenes) instead of searching on unindexed or related fields.
Here is an example. Let's say you have a Contacts database where the contact's phone numbers are in a related table. If you were to go to the contact's layout and search a phone field, you'd be searching in the related table and on a Million records you'd likely need to go make a pot of coffee. However, fmSearchResults performs that search in the phones table directly and is wicked fast. Then, when you click on a found entry it is smart enough to know that you don't want to go to the phone number's record, but to the *contact* for that phone number.
It does a few other things to speed things up, like trying ideal searches before looser searches (since there is no penalty for finding no records on indexed searches) but that is the gist of it.
Fast. Very fast.
Unless of course you tell it to search an unindexed or related field by accident. ;-)
