iOS will automatically purge any app that is suspended in the background. This can happen to a large FileMaker SDK app when a user changes to a different app and said app requires additional memory. If the FileMaker SDK app is re-launched after being purged it will perform the familiar 'consistency check' to repair any bad blocks.
The question I have is what actually happens when the database is damaged beyond repair? Will the FileMaker SDK app show an error message? What is the error message that appears in FileMaker Go? Am I assuming correctly that neither FileMaker Go nor the SDK app is able to repair a damaged file in the same fashion as FileMaker advanced can?