Thank you for the post.
Using FileMaker Pro 12.0v4 Advanced on Windows 7, I am not able to replicate with the steps provided.
The first suggestion would be to update to the latest version of FileMaker Pro 12 Advanced found here:
After updating, I recommend running a recover on this file to see if it might be damaged.
Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
1. The recovered copy may behave differently even if recover reports "no problems found".
2. Recover does not detect all problems
3. Recover doesn't always fix all problems correctly
4. 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.
And here's a knowledge base article that you may find useful:
If recovery shows no errors, then can you create a new simple test file in FileMaker Pro 12.0v4 (Advanced) that replicates this particular behavior?
Thanks TSFalcon, thanks for replying..Okay, I will update the version today only and post my results here.
Updated the Filemaker Pro 12 Advanced client to FileMaker Pro 12.0v4 Advanced. Still no luck:(. I am seeing same issue. Any further suggestions will be highly appreciated.
What happened when you recovered the file?
Do you have any back up copies made before the file started crashing?
If you create a small, brand new file, and try these same steps, does FileMaker crash?
If you try it on the original file, but on a different layout do you get a crash?
Thank you for the reply.
PhilModJunk's questions and troubleshooting suggestions are all good ones.
Since you've updated to the most current Windows version of FileMaker Pro 12.0v4 (Advanced) and the issue persists on multiple computers, the next step will be to take a closer look at the database file as the culprit.
Testing with a new file will help determine if we are dealing with a crash caused by corruption in the database file.
Testing the same file but a different layout will help to isolate possible corruption.
Testing an older copy of the file will help determine if corruption has occurred since modification of the current copy.
Keep in mind this section of the FileMaker Forum, "Report an Issue" is for reporting possible product bugs with the FileMaker application. Corruption specific to a single file is not a FileMaker application bug, and any issue report forwarded to Testing and Development will need to be reproducible in a new file.
Thanks all for responding..I tried on a new file and it is not reproducible. That confirms, this is most of a file issue rather than a filemaker issue.