I’ve been working with FileMaker for over 20 years and the question that always arises is ‘Why do you use FileMaker?’ or ‘Is FileMaker the right platform to develop our database on?’.
This is part 2 in a series of blogs where I try and answer that question as best I can. You can read part one of the story here.
Part 2: Speed.
What happens when my FileMaker database starts getting quite large, say over a million records, will it still be quick?
As long as your system is well designed then it can easily handle large numbers of records, from tens of thousands to millions. We’ve designed systems that can search and display the results, on sets of data over a million records, in only a few seconds. But if you don’t design your system to be optimised for speed then, like any platform, FileMaker can slow down and make the usability of your system tedious. Making sure the relationships in your system are optimised for the purposes you require and that relevant data is indexed correctly can make all the difference to the users experience.
So even with a complex system, running large sets of data, FileMaker can still manage your data efficiently and quickly.