Jana, You should have a copy of the Clones folder in your database, as well as all the folders, ideally in the same structure as ebase was provided to you from TechRocks. The best strategy is to back up the entire copy of ebase - all data files and folders - and restore as needed from that backup after deleting the entire ebase database folder. I can't comment specifically on how to restore since that depends on how you back up in the first place. In any case, yes, restore the "clones" folder. If you have properly deleted the entire ebase database, you'll need to also restore the "documentation" folder as well (unless you have copies of them elsewhere).
Now, having said all this, it is safe to move the ebase documentation to another area on the hard drive or shared folder so you don't have to back up those files every time. If you do this, you should still keep a backup copy of the documentation files somewhere, but since they won't change, you don't need to restore them. Carl pwf wrote: > > Thank you Carl. I deleted the contents of our original ebase folder. Now, I > want to copy ebase from our Backup Folder into our orig. folder (which is a > shared folder, between one coworker and me). Along with all the files, do I > need to also copy the "clones" folder and "Ebase Documentation" folder? > (These are in our Backup folder and I don't know enough to know how > essential these are to using ebase, if at all). > > Jana > > -----Original Message----- > From: Carl Paulsen [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 01, 2001 10:20 AM > To: TechRocks Support > Subject: [support] Re: damaged "names" file > > Jana, > > This is potentially REALLY dangerous and I highly recommend just > recovering from the entire backup - just trash your current damaged copy > and restore from the backup. > > Here's why. If anything in the files has changed since you last backed > up, the old names file doesn't necessarily jive with the other > associated files. Here's a simple example of what I'm talking about. > Let's say you've added a new name and payment into the database before > the crash. Your old names file won't have that record in it, but the > active database will have a payment associated with that person's record > number (let's say it's #2310 in the damagaed names file). Remember, the > payment info lives in a different file than the names. Now, as you > re-enter data, you may put a different name into the record #2310 spot. > Now, voilla, that old payment info for a different person will be > attached to this new person who perhaps hasn't given yet. Other similar > problems can occur with actions or source code records, etc. In > addition, there are three other files that work int he background that > keep summary data on each record that can get majorly messed up if you > re-assign record numbers for names. > > Multiply these problems by however many changes you may have made to the > database between backups and you can see how complicated this problem > can become. You save yourself MANY headaches by just restoring the > entire database. > > This problem also highlights the importance of backing up the entire > database, not just the names and/or payments data. > > Carl > > pwf wrote: > > Our Ebase was not properly closed. When opening Ebase, that message > appears > and then a message stating the Names file was damaged. I removed the > names > file from the Ebase.102 then copied a backup of names back into Ebase. > It > seems to have worked. But, is this a bad way to go....just replacing one > file > rather than using our entire backup copy? Could other files be damaged > too > (i.e. payments, etc), even though things seem to be working fine? Shall > I > proceed differently? > Thank you > > Jana Reister > Professional Women's Fellowship > 206-382-7276 > [EMAIL PROTECTED] > > -- > Carl Paulsen > New Hampshire Rivers Council > 54 Portsmouth Street > Concord, NH 03301 > 603-228-6472 > 603-228-0423 Fax > [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 > --------------------------------------------------------------------- > > ------------------ > 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 > --------------------------------------------------------------------- -- Carl Paulsen New Hampshire Rivers Council 54 Portsmouth Street Concord, NH 03301 603-228-6472 603-228-0423 Fax [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 ---------------------------------------------------------------------
