
Moin Moin,
Unfortunately, in the past it has often happened that FileMaker databases are hard terminated or "shot down" due to power failures, tripping over cables or similar incidents. When this happens, FileMaker can no longer close the database correctly and file corruption can occur. The next time the database is started, FileMaker therefore carries out a consistency check in each database file.
I always recommend running the databases on a FileMaker server, especially if further development work is being carried out on the database, where the developer may well end up in an endless loop or similar that cannot be aborted. Because if the databases are released from a server, it is irrelevant for the databases if the client crashes. However, the server should also be a stable machine - if it runs unstable due to misconfigurations or similar, nothing is gained, of course... ;-)
Greetings from Kirchhatten
Markus Schall
gofilemaker.com - MSITS
The forum for the Claris FileMaker-based gFM-Business ERP software with CRM, merchandise management system and invoicing for Apple Mac, PC and iOS. It serves the exchange between users, developers and gofilemaker.de. The forum boards are divided into overarching topics and modules such as customer management, merchandise management or invoicing. Anyone interested is welcome to actively participate in the forum.


