|
We are having some serious problems with Ebase
crashes. Before quitting, the program will give a Filemaker error warning
saying "Filemaker is unable to read the disk this file is on". The error
is with the Summary_.102 file. I have had these problems before, and in
worst cases have had to restore a former version of Ebase from a zip
back-up. Many months ago when this type of error message first occurred, I
used the restore function as detailed in the Ebase administrator manual.
The problem seemed to correct itself. Much to my horror, I read on the
Listserv that you should never use the Restore function as it can cause serious
future problems. Now that Ebase seems to be frequently quitting, am I
to assume that all of my back-ups since I used the Restore function are
corrupted? If this is the case, is there any way, short of going back to
pre-corruption data, to resolve this problem?
Katherine Dowson
Teton Regional Land
Trust
------------------ 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 --------------------------------------------------------------------- |
- [support] Re: Ebase Crashes Joann Grant
- [support] Re: Ebase Crashes Dave Shaw
