Hi all -
A funny thing just happened. While using the internet, without warning my
computer shut down, as if someone had just pulled the plug. Ebase was up and
running when it happened. I started up again, and started ebase to check it
out. Everything looked fine, filemaker ran its consistency block check, and
i started poking around in different screens to see if they opened up ok.
Each time I opened up a screen, e.g. payments, actions, contacts, etc., a
window would pop up that said "this was not closed properly...", and would
then quickly go away, leaving the screen normal. Everything seemed fine.
Then I went into Output, then Response Analysis, at which point Filemaker
performed an illegal operation. I've since found out that the summary.102
file is damaged, and I should use Recover (which I know I shouldn't use).
Question 1 is: anyone know why this might have happened?
Question 2, the basic one: I have a zip disk with a backup, which I want to
use to replace the corrupted file. What is the exact procedure for replacing
ebase with the backup copy? Do I just delete summary.102 from the hard drive
and then copy summary.102 from the zip disk onto the hard drive? Or should I
replace all the files on the hard drive, since I'm not sure if summary.102
is the only damaged file? Basic, I know, but any input would be appreciated.
Cheers,
Kevin Haskins
Portland Trails
1 India St.
Portland ME 04101
[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
---------------------------------------------------------------------
