Filemaker fmdiff change creator version how to#
Filemaker fmdiff change creator version install#
Filemaker fmdiff change creator version windows#

So you may still have problems with the information in your file itself (ie. > Note: The consistency check does not actually verify the data stored within the fields in your file.

This actually isn’t entirely necessary but we will go over your other options later. When FileMaker Server 9 detects any problems during it’s inspection it will suggest to use recover on the file. Verifies that the next and previous blocks are there Asserts that block structure is intact – 4K Blocksġ. The consistency check performs some cursory inspection on the file to check for common types of corruption. What these people are experiencing is FileMaker 9 Server’s consistency check.

Filemaker fmdiff change creator version install#

This is definitely the point of much consternation because many people have taken these files, which they thought were perfectly fine, directly off their FileMaker Server 8 install and moved them over. FileMaker 9 tells you that the *file is damaged and must be recovered*. The most common way people find out that there is a problem with their file is they fire it up in FileMaker Server 9 and it *won’t open*. I won’t even get into these because things as innocuous as network latency (Extreme cases but you get my drift) may even cause damage to your shared file so *don’t do it*. This may take a while so make sure you are doing this after hours.įileMaker files have many more opportunities for damage when they are not hosted on a FileMaker server. To fix this problem just turn off indexing on the field and then turn it on again (you have to close and re-open the Manage Database window between changes). 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.

Filemaker fmdiff change creator version windows#

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.

Filemaker fmdiff change creator version how to#

One of the most asked questions about FileMaker is how to deal with damaged files.