It may be something as simple as a bad index. > Note: If you are searching in a field and you are getting strange results or for some reason when you go to a layout a script hangs. Whenever your FileMaker Server closes unexpectedly wether it be the application or the whole computer there has likely been some damage to the file. My favorite is when a the night crew comes in and plugs their vacuum in and blows a circuit in your ups causing your FileMaker Server to lose power. Maybe one of those fantastic Windows Server programs decided your FileMaker Server was a virus and shut it down.
Perhaps the power went out and for some crazy reason you didn’t put your FileMaker Server on a UPS (that was **very** not smart). The most common way that a FileMaker file can become damaged is FileMaker Server unexpectedly closing on the server computer. I’ve broken a lot of this down for easy consumption but almost all of this info comes from his DevCon Session. He also gave some very in-depth explanations of what exactly each different option actually does “Under The Hood”. Compact, Optimize or Recover… Maybe `Save as Clone` which one works and why? Hopefully, this will answer a lot of your questions.Īs I mentioned in my FileMaker DevCon: Day 2 article, Jon Thatcher, FileMaker Server guru, gave an excellent presentation on exactly what you should do when a file is damaged.
There is a glut of choices when attacking this problem and there doesn’t seem to be one single answer.
One of the most asked questions about FileMaker is how to deal with damaged files.
0 kommentar(er)
