ArchiwumFileMaker 14: what changed and what to check today
Version 14 is part of the platform’s history. We preserve an account of its direction and practical guidance for businesses that still develop solutions originating in that period.
Editorial comment: September 2026
Scripting and interface design
The former site focused on redesigning the scripting and calculation environment: finding steps, functions and operators faster. This was a change to the developer's daily work, not an automatic improvement of the logic of the existing application.
The UI elements featured included button bars, SVG icons, navigation parts, and field tooltip texts. Their meaning remains valid: navigation and the method of entering data should be predictable for the user.
Mobility and application sharing
Version 14 materials emphasized Go, WebDirect, and cross-device work. Such features must be read in the context of the clients, systems and constraints at the time.
Working with a local file in Go does not automatically synchronize its data with the host. If a legacy solution uses offline copies, their synchronization method is a key part of the audit.
Modernization of the solution from that period
First, we record the versions of database files, client applications, the server, plug-ins and operating systems. We check backups, schedules and integrations, and whether the application can be restored in a controlled environment.
- attempt to open and check the data on the copy
- tests of scripts, printouts, imports and containers
- verification of roles, logins and certificates
- checking for dependencies removed or changed in later versions
- switching plan and return option
What's worth keeping from the old app?
The process model, user knowledge, and data history can still be valuable. Modernization doesn't have to mean rewriting the entire solution. We separate elements that work correctly from dependencies that hinder further development.
We do not carry over past performance promises or licensing terms to our current offering. We check the target product set and environment for a specific project.
From FileMaker 14 to the current platform
An audit helps determine which screens and processes can be retained and which need to be rebuilt. We check mobile clients, web access, data sources and license model separately. Old runtime solutions may require a change in the way they are provisioned.
The current FileMaker 2026 develops, among others: API integrations, working with scripts and AI capabilities. There is no need to implement all new features at once: the first goal of modernization is the efficient operation of the necessary processes in the agreed environment.
FileMaker 14: what has changed in everyday work?
The following overview recreates the scope of the historical FileMaker 14 presentation. It helps identify features used in older databases before modernization.
| Area | Scope presented in version 14 | What to check when modernizing |
|---|---|---|
| Scripts and calculations | Script workspace, autocomplete, in-line parameter editing, script tabs and function descriptions. | Scripts, dependencies and how to diagnose errors. |
| Application interface | Button bars, SVG icons, navigation parts, tooltip texts and object styles. | Navigation readability, field behavior and custom themes. |
| Launch Center | Graphical application list, custom icons and Favorites. | How to open files and access the correct host. |
| FileMaker Go | Keyboard selection for the field, screen orientation control, signature, and image, sound and video support. | Touch scenarios and available device functions. |
| WebDirect | Development of support for mobile browsers and interface on various screens. | Supported browsers, layouts and limitations of features used. |
| Connection to the host | Reconnecting after network loss was a separate topic from the local Go file. | Re-login, unfinished save and offline data sync. |