FileMaker and Microsoft Access are the two longest-standing low-code database platforms for building business applications. Both have been around since the late 1980s, both have loyal user bases, and both are still actively developed. But they have diverged significantly over the past two decades, and the gap continues to widen.
I have built systems on both platforms over the years. This comparison reflects practical, hands-on experience rather than marketing material from either vendor.
Platform Heritage and Trajectory
Microsoft Access was born as a desktop database tool for Windows, and that DNA has never really changed. It remains part of the Microsoft 365 suite, bundled with certain Office plans. Microsoft continues to maintain it — bug fixes, compatibility updates, minor feature additions — but it has not received a major strategic investment in years. Access web apps and Access Services in SharePoint were introduced and then deprecated. The trajectory is one of maintenance rather than innovation.
FileMaker, now under the Claris brand (an Apple subsidiary), has taken a different path. It has evolved from a desktop database into a full application platform with native iOS apps, web deployment, a REST API, server-side scripting, and cloud hosting. Claris has invested heavily in the Data API, JavaScript integration within FileMaker, and the broader developer ecosystem. The platform is actively growing.
This trajectory difference matters. When you choose a platform, you are not just buying today's features — you are betting on where the platform will be in five or ten years.
Cross-Platform Support
This is the most straightforward comparison point. Access runs on Windows. Only Windows. There is no macOS version, no Linux version, and no native mobile application. If your team uses Macs — increasingly common in creative, professional services, and technology companies — Access is simply not an option without virtualisation or remote desktop workarounds.
FileMaker runs natively on macOS and Windows. FileMaker Go provides a full-featured native client on iPad and iPhone. FileMaker WebDirect delivers the application through a web browser on any platform. A single FileMaker solution can serve users across all these environments simultaneously, from the same hosted file.
Web and Mobile Access
Access has no built-in web access. Microsoft deprecated Access web apps in 2017, and Access Services in SharePoint Online was removed. If you need to make an Access database available over the web, you are looking at third-party tools or a complete rebuild using Power Apps or another Microsoft platform. Mobile access follows the same story — it does not exist natively.
FileMaker WebDirect allows users to access the full application through a browser with no plug-ins or downloads required. It is not a simplified web view — it renders the same layouts, runs the same scripts, and enforces the same security. FileMaker Go on iOS goes further, supporting offline use, local device features like the camera and GPS, and barcode scanning. For businesses with mobile workforces, this is a significant advantage.
Scripting Capabilities
Access uses VBA (Visual Basic for Applications) as its scripting language, along with macros for simpler automation. VBA is genuinely powerful — you have full programmatic control over the database, forms, reports, and external applications. Experienced VBA developers can build sophisticated systems. The language itself, however, is showing its age, and finding skilled VBA developers is becoming increasingly difficult.
FileMaker uses its own scripting language with over 200 built-in script steps. It supports full control flow, error handling, variables, and the ability to call sub-scripts. More recently, FileMaker added the ability to execute JavaScript within calculations and web viewers, which opens up modern programming techniques. FileMaker scripts are also easier to read and maintain than VBA for most developers — the script workspace provides a structured, visual environment that reduces errors.
VBA offers more raw flexibility. FileMaker's scripting is more structured and maintainable. For team-based development, FileMaker's approach tends to produce more consistent, readable code.
Server Deployment
Access databases are files. You can share them on a network drive, split them into front-end and back-end files, or link them to SQL Server as a back end. But Access itself has no server component. Sharing a database over a network is fragile — file corruption, record locking issues, and performance degradation are well-known problems. The recommended approach for multi-user Access deployments is to use SQL Server as the back end, at which point you are maintaining two platforms.
FileMaker Server is a purpose-built application server that handles concurrent connections, manages record locking, runs server-side scripts on schedules, performs automated backups, and serves WebDirect sessions. It is a proper multi-user server. Claris Cloud offers the same capabilities as a managed hosting service. The architecture is designed for concurrent access from the ground up.
Data API and Integration
Access can connect to external data sources through ODBC and linked tables. You can link to SQL Server, Oracle, or other ODBC-compliant databases. VBA can also make HTTP requests, though this requires manual coding for REST API interactions. There is no built-in API for external systems to connect to an Access database.
FileMaker provides a full REST Data API that allows external systems to create, read, update, and delete records, run scripts, and interact with container data. This makes FileMaker a viable back end for web applications, mobile apps, and integrations with other cloud services. FileMaker also supports ODBC for outbound connections, cURL for HTTP requests, and has native support for JSON parsing and generation. For modern integration requirements, FileMaker is substantially more capable.
Cloud Hosting Options
Access has no official cloud hosting option. You can run it on a Windows virtual machine in Azure or AWS, but this is not a managed service — you are responsible for the operating system, Access licensing, backups, and maintenance. Microsoft's strategic direction for cloud databases points toward Power Apps and Dataverse, not Access.
FileMaker offers Claris Cloud, a fully managed hosting platform. You upload your solution, Claris handles the server infrastructure, updates, backups, and SSL certificates. You can also self-host FileMaker Server on your own cloud VM or on-premise hardware. The flexibility to choose your hosting model is valuable for organisations with specific compliance requirements.
Long-Term Platform Viability
This is the question I get asked most often by organisations considering a migration. Access is not going away tomorrow — millions of databases rely on it, and Microsoft will continue to support it. But the writing has been on the wall for some time. Microsoft's investment is in Power Platform (Power Apps, Power Automate, Power BI), and Access is increasingly positioned as a legacy tool. New features are rare. The developer community is shrinking.
FileMaker, under Claris, continues to receive annual major releases with genuine new capabilities. The developer community is active, Claris hosts an annual developer conference, and the platform roadmap shows continued investment in web technologies, cloud services, and API capabilities. It is a platform that is still being built, not just maintained.
When Access Makes Sense
Access still has legitimate use cases, and I would not dismiss it outright:
- Windows-only environments where all users are on Windows desktops and there is no need for web or mobile access
- SQL Server front end — Access works well as a rapid forms-and-reports interface on top of SQL Server, particularly for internal tools
- Existing Access systems that work well, meet current needs, and do not require web or mobile access — if it is not broken, a migration may not be justified
- Microsoft 365 environments where Access is already licensed and the requirement is simple — a quick internal tool for a small team
- Budget constraints — if Access is already included in your Microsoft 365 subscription, the marginal cost is zero
When FileMaker Is the Better Choice
For most new projects that need a low-code database platform, FileMaker is the stronger option:
- Cross-platform teams using both Mac and Windows
- Web access requirements — FileMaker WebDirect provides this natively
- Mobile workforces — FileMaker Go with offline support is unmatched
- API integrations — the Data API makes FileMaker a modern integration point
- Multi-user deployment — FileMaker Server is purpose-built for concurrent access
- Long-term investment — the platform trajectory gives confidence for five- to ten-year planning
- Compliance requirements — flexible hosting options including on-premise
The Bottom Line
Access is a capable tool that has served businesses well for decades. If you have an existing Access system that meets your needs and operates in a Windows-only, desktop-only environment, there may be no pressing reason to migrate. Stability has value.
But for new development, or for organisations that need web access, mobile support, cross-platform compatibility, or modern API integrations, FileMaker is the more capable and future-proof platform. The investment in licensing and development time pays for itself in a solution that can adapt as your business grows and technology requirements evolve.
If you are currently running a business-critical Access database and wondering whether a migration to FileMaker makes sense, we are happy to assess your system and give you an honest recommendation. Sometimes the answer is to stay put. When it is time to move, we can help you make the transition smoothly.