You obviously have very serious data corruption. Your only choice is to go to backups until you find one that is not broken, and then reenter data going forward. If it is too old, you should export all your data; reinstall a clean, empty copy of ebase; and import the data into it. This last step is tricky and you need to read and understand the procedure which is in the archives of this list or hire and expert to help.
WARNING TO ALL: At the first sign of data corruption, strange behavior, whatever out of the normal, STOP entering new data or changing old data immediately. Figure out what is wrong and then proceed after fixing the problem. You don't say what you are doing after a crash. If you do anything other than restore from your previous backup, you are practicing unsafe database practices and have almost certainly made the problem worse. There are a number of consistency checks that one can apply but they are not documented in any consistent fashion and not builtin. Part of running any database is a continuous process of verifying that things are working right, people are entering data correctly, etc. ----- There is a small chance that your problems are caused by lack of resources, either memory or disk space. Replace all Find Fields is about the most stressful thing normally run on ebase. > -----Original Message----- > From: Sue Gilbert [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 08, 2002 7:27 PM > To: TechRocks Support > Subject: [support] Help! > > > Our database won't stop crashing. I've trouble shooted the problem down > to the "Replace All Find Fields" Script. Everytime I run this script the > database crashes soon thereafter. So essentially I stopped running this > script, but lately have found that many of our records in the names file > are not current with the payments file. I've been experimenting with > running the script from a recent start date. I was successful in going > from the beginning of our fiscal year (10/01/01) without any problems, but > when I ran the script from our previous fiscal year (10/01/00) the > database crashed again. Sometimes we won't receive a "damaged file" > message until days after the crash, and hence we're losing our recent data > entry and database work. I'm not sure where to go from here. If I don't > run the "Replace All Find Fields" script, then our data is not current and > already members are recieving mail that they shouldn't. If I run the > script, then the database crashes. What to do? Help! > > ------------------ > 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 ---------------------------------------------------------------------
