Most of FileMaker programming is fairly straight forward and repetitive: Setting up T.O.’s, adding fields, building layouts, and so on. The biggest challenges occur when a solution calls for specific feature or features that aren’t supported by FileMaker.
Then it’s time get creative. And that’s where a of time is spent on a solution, experimenting with various options trying to make FileMaker do something it doesn’t want to do.
And making it work fast, every time, and scalable for multiple users, and so on.
That’s where Kevin Frank shines. Frank has talent for finding solutions of these types, and then takes it further: He often finds more ways to do it, and tests one against the other(s).
Finally, he shares his work with the world on his blog, FileMakerHacks.com.
Recently, Frank decided that the basic FileMaker field index option had too many limiting features:
It’s a great feature, but it has some limitations:
- Field indexes are not found set aware — you get unique entries for all records
- The field must be on the layout (and enterable)
- The field must be indexed
- When viewing a field index, it’s possible to accidentally insert data into the underlying field
- You can’t copy what you see — it’s view only
- If you’re doing a screen share, and zoom the database up to a higher magnification, the index window does not correspondingly zoom
Well today we’re going to look at a technique to circumvent these limitations, and I invite you to follow along in today’s demo file, FM 13 Pseudo Indexing, if you are so inclined.
and took on the task of building a replacement.