FileMaker Pro 11 and Crashing
Operating system version
OS X 10.6.x
Description of the issue
I have been using FileMaker for over 11 years, from version 4, and I have never had so many databases become corrupted in any version until 11. I have had almost every database I manage at some point while using version 11 get corrupted forcing me to rebuild. This is starting to become a pattern and I am getting discouraged that it will eventually happen to every database I manage and create as long as I am using version 11. I send in crash reports when they happen, but that is a black hole. I want to have some assurance that this problem is happening to others and that someone is figuring out the fine points and doing something about it. Rebuilding a database is time that I cannot charge for, and I have had too many non-billable hours dealing with this.
Steps to reproduce the problem
There is no telling when the app will decide to crash, and I send in the reports when it does.
I would expect that FileMaker should not crash EVER, but I know that is not realistic, however it would be nice if I could rely a lot more on it.
When the app crashes, the file has to be recovered, putting in motion either to rebuild immediately (time permitting) or to keep using until the file can be rebuilt (which it has always had to be so far), but either way I am looking at building in to every project I do an additional number of hours that I cannot bill for. The rebuild often causes problems for the client since it usually happens when I am developing new areas of a file and a rebuild must be done with absolute accuracy or the new file will have issues. So the client must now deal with what was previously an approved and working solution in every respect that has to be used carefully lest there be one field or script step that was not carefully looked over to make sure it was rebuilt exactly. ( I can compare this to disassembling electronics, where you are putting it back together and there is a tiny screw left over... where was it supposed to go again?? ) Unfortunately one cannot shoot a video of database development to keep in case the file needs to be rebuilt. Some will say I should be backing up, and I do, but when developing new areas, there is always a number of hours that are lost in returning to 'the last known uncorrupted copy'.
Exact text of any error message(s) that appear
FileMaker Pro and unexpectedly quit.
This problem has happened on a variety of systems, both Mac and PC. I cannot pinpoint a common denominator to any occurrence other than I am using FileMaker Pro version 11.