>Hi,
>This morning when I went into ebase I got a message that said that the file
>"names_.102" is damaged and to do a recover for that file. I did a recover
>for this file and it said it that the process was complete and successful.
However, we learned late last year that the recover process can leave
unrepaired problems behind that don't show up for some time. It's
much more secure to restore from your latest backup and re-key the
work you have done in the last couple of days since the backup.
>Now when I try to get into ebase again, I still get the damaged file
>message.
>What am I doing wrong?
The recover process creates a new file called, in this case,
"names_recovered.102". You need to remove the old damaged file and
change the name of the new file to exactly what the old one was,
names_.102. But again, better to restore from your backup.
--
Dave Shaw Northwest Classics, Inc
tel: 206-954-7526 fax: 206-625-1338
------------------
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
---------------------------------------------------------------------
