Crashes can be caused by file damage and files can be damaged by crashes. Thus, all your files should be run through a recover process to see if any damage is reported. Keep in mind that even if your file was not damaged when it crashed the crash may have damaged it.
Things to keep in mind about Recover:
- 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.
- start FileMaker without any DB
- create a brand new, vanilla DB with some fields, i.e. one text, one number (if I got it rigth, You didn't test with brand-new, no-Data, never used DB's)
-> does FileMaker crash?
-> Does FileMaker 'hang' (taking a loong time to start)?