Thanks Corn, for the clear explanation which is sharp and provides clear
informations.
I will do as you suggest... I work on this file on some hours sessions... I
will work on it and then save a copy, and keep always the copies of last
seven days before.
So, if I well understand recovery is needed only when prompted by an FMP
window. No preventive recovery is necessary.
I still wonder about what happened since the recovery lost some fields and
the full content of a global (which I use as a notepad, i.e. I paste in it
raw data to scatter later in all fields)... anyway.
About the anonimity I want to make it clear that is not due a lack of
respect to the fellow of the list, but I had troubles in the past, when a
customer of mine saw a post from me in a fmp list asking informations... and
argued with me that I was not so well experienced if I had to seek advice in
a list on a program of his I was working on, it was not pleasant, take my
word for granted, if you can.
Second (main ?!?) reason I do political activity (here in Italy) and had
already serious problems (which have costed to me much in a specific event)
because of my web posts and activity scattered on the net and easily
traceable by google. This last episode is not related to FMP activity, of
course.
But since then I made a point to keep an uptight privacy level.
I am ready to disclose my identity (nothing to hide) but on a peer-to-peer
basis on private emails, that as a private matter, I am confident should
remain private material.
Internet has a long lasting memory and until a "right of oblivion"
international protocol will be approved, I don't wanna be judged and
observed for my whole life for something I wrote or did on the web, unless I
am ready to do it by means of official documents, or something issued to the
press, thus a public event.
If this is against any standards, or list policy, I am ready to pay the
consequences and leave (or enter again with a John Doe like name, if
possible).
But I am confident list members will understand this. No offence intended,
all maximum respect given.
Chuck, thanks for your email also.
Kindest regards
MoneyMaker
"The plain art of making Money"
----- Original Message -----
From: "Corn Walker" <[email protected]>
To: <[email protected]>
Sent: Thursday, February 19, 2009 3:01 PM
Subject: Re: Recovery protocol
Good morning Anonymous,
Such a long message... let me see if I can cut to the chase a bit.
There is no 100% way to avoid damaged files. There are simply too many
moving parts where any one of them can cause problems. You should backup
as frequently as you deem fit. That is, if you're comfortable losing two
days of data entry, you only need to back up every two days. If an hour
of data loss unacceptable then you should backup more frequently than
that. A copy of FMS would come in handy in this regard.
You should make a "clone" of the database whenever you make structural
changes (e.g. defining new fields, creating/modifying layouts, etc.). You
only need to keep a few of these clones around - perhaps only those where
major changes have been made. As the database progresses and you don't
encounter problems, you can throw away the older clones.
Recover is only for repairing a damaged file to retrieve data. If you
have a file that has been damaged you can do one of two things:
1) make a copy of your latest clone and import the recovered data
2) revert to your latest backup and reenter the missing data
Saving a compressed copy optimizes the size and structure of the file. It
is the only "preventative" action I would recommend. By no means should
the Recover operation be used as a preventative measure. A copy of FMDiff
might come in handy to help you manage these processes and keep an eye on
the state of your files.
Cheers,
-corn
Corn Walker
The Proof Group
http://proofgroup.com/
