The most common way for a magpie file to get into the procedure is 
for the proper file to be unavailable somehow. FileMaker will put up 
a dialog saying the file is not available, please find it. The user 
then navigates to the correct file. If the user navigates to the 
incorrect file, (or, I gather sometimes just cancels, and FileMaker 
goes looking on its own) some other similarly named file gets 
substituted.

In this case, if I'm hearing right, make the file names_copy.103 
unavailable. Copy it to an external drive, throw the original in the 
trash, and empty the trash. Then start ebase. When  you get the 
dialog asking for names_copy.103, navigate to the new, repaired, copy 
of names.

Of course, the usual comments apply - restore is a dud, go to the 
most recent backup to avoid future problems.

>Jack, Clif, Bob or others,
>
>I'm trying (long distance) to help someone fix a database gone bad
>(because of a crash) but have encountered an odd problem.  When opening
>ebase with Filemaker (using ebase.103), the user is required to enter
>two passwords, one for ebase.103 and another for a file called
>names_copy.103 (or something like that).  This file is the name of a
>"backup" copy of the names file kept on a local zip disc (although
>perhaps it was created when the user tried unsuccessfully to run the
>recovery procedure???).  No other ebase-related files will open until
>this second file opens (same password).  Once opened, the names file is
>opened next - or Filemaker tries to open it, but it is damaged. 
>
>The user tried to run the FMP recover procedure, but because they didn't
>understand it, they seem to have aborted it.  Unfortunately, there's no
>way for me to know for sure what happened when they tried to run the
>recovery procedure. 
>
>I thought the ebase.103 file ran a script to open the other files, but
>how could this new file have gotten into the queue?  I have no access to
>the ebase.103 file so can't look in there to see if there's a problem
>there.
>
>Can someone shed light on the "open" sequence and where such a file
>might have gotten plugged into it?
>
>Carl
>--
>Carl Paulsen
>New Hampshire Rivers Council
>54 Portsmouth Street
>Concord, NH  03301
>603-228-6472
>603-228-0423 Fax
>[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
>---------------------------------------------------------------------

-- 
--
Dave Shaw         H4 Consulting
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
---------------------------------------------------------------------

Reply via email to