Do the other computers access the same files?
What comes to mind as I read your post is that you may have a damaged file that functioned without issue (but was nonetheless damaged), until you updated and then you get a crash.
The POS machine may be having this issue when the others don't due to either accessing a damaged file not accessed by users on the other machines or because it preforms scripts, accesses, layouts or tables that the other users do not.
It would thus be a good idea to run a recover on each file that is regularly accessed from the POS machine.
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.
And here's a knowledgebase article that you may find useful: What to do when your file is corrupt (KB5421).
As always, thanks for your help.
The other computers do access the same files but the problem computer is the main cash register and gets much more action.
Thank you for your posts.
From one of the crash reports, can you display the header and the crashed thread? This will help point to a possible cause.
FMP 13.0v5 would usually freeze up and I would not get an error message.
Interestingly, yesterday, I used FPM 12.0v5 on the problem computer and it worked fine! It was MUCH faster and did not freeze or crash. Recall that FMP 12 is not supposed to be compatible with Mac OS 10.10.2, which is the OS on our server and all clients. I must assume that the FMP 13 app on the problem computer was the issue. I plan to uninstall FMP 13 and re-install it. Does that sound good?
Although FileMaker Pro 12.0v5 was neither tested nor certified under Mac OS X 10.10, it does appear to work. Therefore, uninstalling and reinstalling FileMaker Pro 13 would be a good approach. If it still fails, create a new user account, login to the user account, launch FileMaker Pro 13 and see if the freezing still occurs.
I would still take at least recent back up copies and run recovers on them to see if any come up damaged, just to be sure.