It sounds like FileMaker is crashing. Are they opening a file hosted from another computer or opening a file local to their machine (or both?).
Database is stored in the FileMaker server we have here in our office. The file is local to our stations.
What do you mean by "The file is local to our stations"?
Does that mean that your user is opening a file on the workstation that then connects to a hosted file on the server?
My bad, well no, everything is stored in the FileMaker server. We navigate to the network and then the database.
We navigate to the network and then the database.
Do you use Open Remote to find and open the database?
If you are not using Open Remote, you have a major problem that could be damaging the database.
I am assuming at this point, that the user launches FileMaker, uses the Open Remote method to find the hosted file and open it and then get's the crash.
If this is only happening for one user, then either they are doing something different--even accessing different records could be the "difference" or there is an issue with their workstation and/or copy of FileMaker.
Here's a test that you can try to help narrow down possible causes:
Create a simple test file of just a few fields and just one layout. Host it on your server. Have your user that is getting this crash attempt to open it from the server using Open Remote. If they can open this file without problem, it suggests that your file may have a problem even though it hasn't crashed for other users. Take a recent back up copy and run a recover on the file to see if any problems are found.
If they get crashes with the test file, you'll need to run diagnostics on the work station to check for trouble and you might try uninstalling and re-installing FileMaker.
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).
If we have a local test database it works well. The odd thing is that it is 2 different computers at the same desk (one at a time). I can set up a new pc else where in the building and it works ok.
Yes, but if you HOST that test database from the server, what happens?
It does the same thing, plus one of the computers was a fresh set up of everything
"Does the same thing" as what--the other hosted file or when it is opened locally? It crashes or stays open?