Todd, You may be in luck. ebase.100 stores no data, it's only used to maintain the integrity of the system, so it never changes. Therefore, an old copy is identical to a new one. If all your other files are OK (you're really, really sure of this?), you need only retreive an ebase.100 file from *any* backup and use it to replace the damaged one. Nothing else is necessary.
Gary > Subject: using recover function > From: Todd Kolze <[EMAIL PROTECTED]> > Date: Wed, 7 Nov 2001 16:35:21 -0800 > X-Message-Number: 7 > > Hi, > > I had a crash and when I tried to reopen the message said that > ebase.100 was corrupted and to use the recover function on it. I > have read the info on this list serve about how the recover function > has problems that don't show up until much later and shouldn't be > used...... > > I didn't have a good recent backup so my plan was to use the recover > function and then export the data that had been entered since the > last back up and then import that data into a clean ebase (the most > recent backup)..... > > My question is: Does it make any difference that I used recover on > ebase.100 as opposed to a data file? I guess I'm trying to cheat > things, the recover I did (about a month ago) is still running fine > and I hesitate to go through all the export and imports work...... > > Thanks much, > todd > > > > > > ***************************************************************** > Todd Kolze > Development Coordinator > Project Underground > ------------------ 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 ---------------------------------------------------------------------
