Crashes can damage your file and damage to your file can cause crashes. For both reasons, running a recover on your file to check it for damage would be a good idea.
And while uncommon, hidden damage to a file can be present and yet your file functions normally until you update/upgrade the OS or the FileMaker version so it is possible that latent corruption is the cause of your original crash.
Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
- The recovered copy may behave differently even if recover reports "no problems found".
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
And here's a knowledgebase article that you may find useful: What to do when your file is corrupt (KB5421).
Thanks for the response. However, I must not have been clear in my post. This issue is not file related but application based. We have been using FMP for 20 years and are very familiar with the file recover process. There is no file open when we close the application. In fact, we can open FMPA and then immediately quit it and get the crash report.
Thanks for the clarification. Many folks equate closing their solution with quitting FMP as they usually do both simultaneously.
Small comfort here, but this isn't typical for FMP 11v4 on the Mac OS or we'd have gotten piles of issue reports on it quite some time ago.
You might try the usual quick fixes for a problem fileMaker app on the Mac OS:
Remove all FileMaker plug ins and see if that makes a difference.
Remove the application preferences file to the desktop and launch again to see if you still get a crash.
Re-install the application.
Quick update. I re-installed the application and everything is working correctly now.
Thanks for the help.