>From the traffic I have seen on this issue, I am about 99% certain that
there is nothing wrong with your disk or you copy of the program. Try
opening your last backup. I bet that works. If you ever crash your machine
with FileMaker files open there is a high probability of damage to one or
more of the ebase files. The damage can result in crashing FileMaker on
startup, the problem you are seeing, insideous changes to the file that may
show up months later. I have seen all of these happen.
As a general problem solving technique, if you are getting ANY strange,
unexpected behavior, try what you are doing on a backup before looking for
more obscure problems. If the backup succeeds, the answer is almost
certainly that your live data is damaged. At that point it only a question
of whether you can play catchup from the last backup or get an expert to try
to recover as much as possible from the failed version. If the backup also
fails, in a similar fashion, go to the backup of the backup, etc. The next
step should be to take your data to a different machine and try to run it
with the distribution runtime version, replacing the sample data with your
data. If this works you know your data is ok and that something obscure is
wrong with your normal machine. For most people a complete reinstall of the
OS on the broken system is the easiest path if you don't have a handy wizard
available.
------------------
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
---------------------------------------------------------------------
