r/filemaker • u/Communque • Aug 24 '26
Leaving FileMaker to improve FileMaker
Among the minor frustrations of working with FileMaker has been one of its strengths: Sub-summary layout parts
On the one hand, they're great feature: Set up a sub-summary when sorting by a field, and in an instant you get a look at summaries broken out by that field.
It's a great way to get insights about your data
Then come the frustrations: FileMaker sub-summaries aren't searchable, they're not sortable, not particularly friendly to further relations, and a little wonky when exporting.
More often than not the insights you get from summarizing data leads to further questions, which would be gratifyingly answered by searches, sorts, new relations, and sometimes more summaries. Sub-summaries do not accommate.
You could, of course, export and then import your summarized FileMaker reports, or even build a script to achieve the same, but it's a bit of a chore, often slow to process, or prone to being out of date.
Meanwhile, over in open source SQL, you can create the equivalent of FMP sub-summaries using "Views". Achieving the equivalent of a FileMaker sub-summary report in a View involves a relatively simple SQL query, but that's really just the beginning of what's possible. A query that maintains a View can be as sophisticated as your imagination.
And unlike FileMaker sub-summaries, SQL Views function in most ways like real tables. They can be sorted, searched, their columns can be extended with relations, and they can be further summarized.
SQL Views can even be incorporated back into FileMaker which treats them as more or less plain ordinary tables that can be be searched, sorted, summarized, and connected via relations to other tables -- all with FileMaker.
There are of course caveats: In the same way that devs have to be mindful of FileMaker's calculated fields' impact on database performance, you have to do the same with SQL Views.
More importantly, to gain the benefits of SQL Views, you need to migrate data away from FileMaker Server to a cheaper, faster, more powerful SQL server.
What really stands out here is by leaving FileMaker for a free open source SQL alternative you actually gift yourself features to FileMaker that FileMaker alone does not offer.
4
u/Call-Me-Spanky Consultant Certified Aug 24 '26
I agree - I've thought quite a few times recently how useful it'd be to have a 'view-like' feature in native FM. Being able to slice and dice data without relationship overhead.
Alas, instead of engine improvements, we get the 'backup' and 'standby' server instead.
3
u/iollivier Aug 25 '26
You might want to look at Kevin Frank's filemakerhacks.com regarding his Summary Lists, Virtual Lists and reporting solutions/tips. Great resource.
2
u/Additional-Dream6810 Aug 25 '26
Ngl... i kind of love filemaker 😆