>We were working on our database, entering payments, when the
>computer froze up. We were not able to unfreeze the computer, so we
>had to force quit the computer. Upon restarting the computer, we
>were not able to access our names.103 file. (The file that
>automatically loads each time we start ebase) A dialogue box
>appeared which stated names.103 deleted or lost...please recover to
>access. So we recovered the names.103. Now, every time we start
>ebase, we are told that we can not access names.103, and that we
>must recover it. We then go to file open, and open
>Recover_names.103.
The best path from this situation is to abandon the current file set
and restore from your most recent backup. FileMaker's recover process
sometimes leaves unresolved problems in the file that might not show
up for some time. If you don't have a backup you can work from, the
restore process is your next best shot.
>How do we get it so that it automatically goes to recovered names file?
Remove the file names_.103 (the damaged file) from the directory. Set
it somewhere else until you have ebase running again, but you will
eventually discard it. Rename the file names_recovered.103 (the
recovered file) to names_.103. The scripts and references in ebase
will now look for the new file. If you have been running ebase with
the recovered, renamed file, some of these references might have
already been changed to the new file. In that case, you will
occasionally get a dialog box that says, "names_recovered.103 can not
be found and is required to complete this operation." Navigate to the
new file (the one you recovered and renamed to names_.103).
Eventually you'll change all the references and ebase will operate
normally.
>Is it OK to be using this file?
Not really, see above.
>Should we rename this file?
Yes, it should be named exactly what the damaged file was named,
i.e., names_.103
>Did we corrupt our database?
Probably. Again, if you have a backup your best path is to restore
from the backup and re-enter data you have entered since the backup.
If you need to use recover, it will at least get you running. Then
work on a backup strategy. Good advice on this in the ebase web site.
--
Dave Shaw Northwest Classics, Inc
tel: 206-954-7526 fax: 206-625-1338
------------------
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
---------------------------------------------------------------------
