Re: Fields Suddenly Missing and Changed - Corrupt file?
by lynn » Wed, 13 Oct 2004 01:04:54 GMT
oug < XXXX@XXXXX.COM > wrote:
Unfortunately for your friend, the "Recover" command in Filemaker does
not repair files. It only opens them to a state where you can recover
all or most of the data.
This is poorly documented, but if you search, in the Help it says
specifically NOT to continue to use or develop crashed and recovered
files. This is why it's prudent to keep uncrashed clones and import the
data from crashed files, then continue to use & develop the clean files.
If your friend doesn't have clean clones, then he will have to rebuild
from scratch. Period. There is no saving the old files...only the old
data. Then you can have the Why We Back Up talk with him...I'm sure this
holds true for Access as well as Filemaker.
[snip of corruption description]
When the Recover command is run, it will examine all the structural
elements of the files, and if it finds anything suspicious to the
analysis algorithms, the suspicious element is REMOVED. Entirely. Field
definitions may be replaced by unnamed fields, but you'll lose
calculations, relationships based on those fields, script steps that
refer to the bad field, etc. ANY element, from layout objects to entire
scripts, can be deleted during the process.
This pretty much explains what you find. Crashing during use,
particularly during defining fields, will cause corruption. Repeated
crashing and recovery will build corruption on top of corruption.
This is one really good argument for hosting files with FM Server.
Usually a client machine crash doesn't affect the hosted files, and a
properly configured server almost never crashes.
Don't continue to use the files. Rebuild them, and then keep the clones
as recommended above. So you'll only do it once. However, you also need
to examine the reasons behind the crashing. Is he hosting the files and
allowing others to guest in inappropriately? Is his machine unstable for
other reasons? Minimize the necessity for importing into the clones by
getting rid of the underlying cause, the crashing.
Nope. Those files are hosed. Thoroughly.
Probably not. I know they want to stop offering that service, and
anyway, Claris became FileMaker Inc. about 7 years ago. ;) The files
themselves won't do you any good, it's really the data you need. Doesn't
your friend have ANY recent backups? If not, shame on him. He'll have to
consider this his Wakeup Call from the Data Gods.
Doug, you're a good friend. Teach your buddy how to post and ask his own
questions, so he can figure out how to rebuild his files, practice good
database hygiene and rigorous backup procedures, and get righteous with
his data. ;)
Lynn Allen
---
www.semiotics.com