I had to "Force Quit" FileMaker while using my database; why is this bad?

Using "Force Quit" to exit or terminate an application is almost always a last resort as it can have unexpected effects on your applications. With Filemaker databases using "Force Quit" leads to corrupt database files. Only ever use this as a last resort.

FileMaker Server will also run a consistency check on databases which have been forced closed.

If you have issues with your database after having had to "Force Quit," luckily ODI keeps backups of your database. To download a backup of your database please read this knowledgebase article.
  • 1 Users Found This Useful
Was this answer helpful?

Related Articles

Filemaker Error Codes

  Error Number Description -1 Unknown error 0 No...

FileMaker Admin Console not working after Java update

FileMaker, Inc. has identified an issue with a recent Java update from Apple that removes the...

Unable to launch FileMaker Server Admin Console

  ISSUE:You are unable to launch the FileMaker Server Admin Console. Attempting to launch...

Filemaker Operating Systems Compatibility

APPLICABLE TO:All Versions of FileMaker Pro System Requirements and Compatibility FileMaker Pro...

My database doesn't show up in the "Open Remote" dialog window (MAC)

You may be having issues seeing your database in the list of files when you open Filemaker and...