Quick Find Power Mode
Who doesn't like the simplicity of using a single field to search across many. That's essentially what Quick Find is. In fact, by default FileMaker makes the silly assumption that every field you add to a layout is something you want the user to be able to search.
Essentially, you want to take control of the user experience in terms of search and make sure the user is not only searching what you want them to search, but also able to search in a fashion which is both familiar and comfortable.
This technique file and video will walk you through the details needed to take full control of the Quick Find experience. You can enforce desirable effects such as sorted record sets and keep the user within the search field ready for multiple repeated search attempts.
By taking advantage of a variety of FileMaker features, we can create both an easy-to-implement and universally powerful Quick Find feature. Watch the video and use the associated technique file in order to have a better understanding of how Quick Find truly works within FileMaker Pro.
Comments
Video Download
HI there does not seem to be a video download link for this article.
No video download link
You will note that this video is hosted on YouTube. As such, it is free to access even if you're not a subscriber, so there's less of a requirement for it to be downloadable.
--
Daniel Farnan
Ignorance is curable, not preventable
Power Quick Find zip.file
Is the downloadable zip file intended to be not modifiable? I am trying to look into the detail but it appears I am unable to.
Thanks.
filemaker version
Hi Matt, is there a minimum version that this needs to run? I ask because I have 17 and the list does not narrow when I type letters into the search field. Is there a change that would need to be made to make it run on 17?
Hello Matt
Seems that FileMaker changed something since you created this video, as search as you type no longer seems to work, and the find is only performed by either leaving the search field or hitting the Return key.
Any idea why that might be? I suspect something changed in how the OnSaveObject script trigger works.