I've learned from cruel experience not to Recover. In the old days before we
used FileMaker Server, we had lots of crashes and I sometimes used Recover.
Only much later did I discover that there were numerous mangled or missing
records in the recovered files. It's easy to overlook when you have
thousands of records. By that time, some information was permanently lost.
If a file is damaged, *always* go to backups. Replace the entire set, not
just the damaged file. That's the prevailing wisdom. If necessary, recover
the mangled file and use it to (manually) extract the newly added data,
including related data, which can then be added (manually) to update the
backups. Recovery is a desperate move - don't trust it.
My suggestion is frequent backups (we do four a day, which are automated)
and don't file away the original hard-copy documents until the next backup.
Every few days, perhaps weekly, make a backup that's kept permanently. Keep
all other backups at least a week. Always keep them on removable media.
Ideally, keep some of the permanent backups offsite. Otherwise a fire could
destroy not only your desk but your ability to raise the cash to replace it.
Gary
> Subject: RE: Damaged File
> From: "Walt Daniels" <[EMAIL PROTECTED]>
> Date: Tue, 3 Apr 2001 15:13:44 -0400
> X-Message-Number: 5
>
> Most of the wisdom on this list says DO NOT RUN RECOVER. It is know to
> occasionally produce files which look ok but have subtile defects that
> sometimes show up much later. It is better to take the time hit and go
> with
> a backup of the whole set of files, not just an inividual file (although
> you
> may get away with that if you know exactly what files have relationships
> with other files.)
>
> > -----Original Message-----
> > From: mwsmith [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, April 03, 2001 2:46 PM
> > To: TechRocks Support
> > Subject: [support] RE: Damaged File
> >
> >
> > *** EBASE DAMAGED FILE RECOVERY ***
> >
> > To repair a damaged eBase file you must run the "RECOVER"
> > function which is available under the full version of File Maker Pro.
> >
> > 1. Select FILE | RECOVER... and selected the damaged file to
> > recover, 'deleted.102'.
> > 2. FileMaker will repair the database.
> > 3. Once completed, open eBase as usual.
> >
> > Regards,
> >
> > Michael W. Smith
> > MWS Consulting
> > Vancouver, BC
> > Canada
> > ===========================
> > Web Site: www.mwsconsulting.com
> > Email: [EMAIL PROTECTED]
> > ===========================
> >
------------------
Reminder to each recipient: To change your list account preferences, go to
http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address
you used to subscribe to the ebase support list:: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
---------------------------------------------------------------------
ebase - Relationship Management for Nonprofits, http://www.ebase.org
---------------------------------------------------------------------
