If a FileMaker Pro database file hangs or crashes when you switch to a particular layout, the layout may contain a damaged or corrupted object. If this happens, try deleting the corrupted object. This may be difficult, however, as the corruption may not be visible. Corruption may also cause FileMaker Pro to crash or hang when it tries to display the object, making the object hard to isolate and delete. In many instances, the simplest and sometimes only solution is to delete the entire layout, which also deletes the corrupted object.
If the problem persists, recover the file using the Advanced Recovery Options dialog box. Select Copy file blocks as-is and
only Bypass startup script and layout. This combination of options creates a new database that is a copy of the old one. When FileMaker Pro opens, it switches to a new blank layout, and the On Open script option is disabled. (For more information, see
Setting advanced file recovery options.)