Any time you get a crash, you need to check your file for damage. Damage to your file could be the cause of the crash and the crash itself can damage your file.
Run a recover on your file and see if any issues are found. Test the recovered copy even if no issues are reported as found and fixed to see if it exports reliably.
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.
Thanks for your help and advice - the Recover did not throw up any identified problems, but it seems to be working ok on the Export. I'll take more time over this tomorrow and check it out fully.
If recover fixed the problem, it may be due to the fact that recover rebuilds all the indexes in the recovered file from scratch. If so, you may want to test a copy recovered like this:
If you have FileMaker 11 or newer, you can use Advanced Recovery options to rebuild your file's indexes:
- With the file closed, select Recover from the File Menu.
- Select "Use advanced Options"
- Select only: "Copy File Blocks as-is" and "Rebuild Field Indexes Now".
This produces a file where the only change was rebuilt indexes and it thus should be safe to use to replace your current file and avoids the need to import a bunch of data into a clone of a back up file or to risk using the original recovered copy.
Tried that, but it won't Export and just closes down.