Hello Eli,
I agree with Jack.
However, that being said, you might still want to know that Summary is in a one-to-one
relationship to Names (meaning that every Names record has/should have one and one
only related Summary record. And the Summary record is full of unstored calculations,
the only stored field being the Record Number field that connects it to Names. What
this means is: Summary is the easiest file to replace. Unless you've customized it in
some way, all you would need to do is:
*Put your damaged version of the file into a folder somewhere away from your Ebase
files and zip it, then trash the original.
*Get a fresh copy of Summary (from disk, Ebase website, etc.)
*Import RECORD NUMBER ONLY from Names or Profile into Summary. (don't try this whole
thing unless you know how to do this step.)
*Put the newly-filled Summary file in the folder with your other Ebase files.
This should fix that file, assuming nothing is wrong with the data itself. Heed
Jack's warnings, though. I too have seen plenty of damage that wasn't immediately
obvious creep up and bite folks later.
HTH,
Matthew
At 09:44 AM 9/7/01 -0600, you wrote:
>Very seldom is there just one file that is corrupted. There may, indeed,
>be only one file that is so badly damaged that Filemaker can no longer open
>it. Unfortunately, most users unintentionally exacerbate the problem by
>pointing Filemaker to the incorrect file(s) when they see the message that
>the file can no longer be opened. If done using the master password, this
>will permanently change file pointers within the ebase
>application. Relationships no longer work correctly and confusion reigns.
>
>There are lots of times when someone who knows Filemaker and ebase very
>well can "fix" a damaged system. This may well be one of those times. The
>larger question becomes one of convenience and affordability. Can you
>afford the 2-4 hours of consulting time it would probably take to fix
>it? Do you have access to such a person? How long can you afford to be
>without your database if you need to send a copy of it to such a person in
>order to have it fixed?
>
>In most cases, the path of least resistance is to go to your
>backup. Again, ebase is a system of files, and I *highly* doubt that only
>your summary_.103 file is corrupted. Whenever you restore from backup, you
>need to restore all of your ebase files as a unit.
>
>>Hi, this is my first time contributing to the list serve and I've heard
>>great things about the things one can learn here.
>>
>>So here goes.
>>
>>Somehow, we think because the program was shut down improperly, the file
>>"summary_.103" became damaged. It is the only one that seems to be that
>>continues to cause problems. For instance, an error message pops up every
>>time I try to add a new name. As well, the payments and contributions say
>>things like "<file missing>".
>>
>>My three questions are :
>>
>>1) What does "summary_.103" do?
>>2) How do I(and should I) replace the damaged one with a backup copy?
>>3) Will I lose all the information added since the backup copy?
>
>---------------------------------------------------------------------
>Jack Noll - ebase consultant and wildlife advocate
>
>Check out a *great* program at www.beardogs.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
>---------------------------------------------------------------------
>
>
Matthew Scholtz
Database and Non-Profit Technology Consultant
Bellingham, WA
Also associated with NPower, Seattle
www.npower.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
---------------------------------------------------------------------
