>By way of background: we were running e-base 1.02 over a network and the
>network kept freezing up (probably not because of e-base). Anyway, I had to
>use the recover command to restore several of the files. Everything is
>working fine, except the delete records feature.
>
>When I run the script I get an error message saying e-base can't find
>'deleted_.fp3' and the script fails. We are running e-base from fmp5. I
>tried renaming the deleted_.102 file and that did not work.
>
>The delete found records command does not work because contacts_.102 is
>password protected.
>
>Any suggestions?
FileMaker's recover command is not as robust as we would hope. The
recover process often leaves errors behind that don't become apparent
for some time.
If the deleted_.102 file were the only file damaged, it might be
possible to replace only that file with a backup. It is one of very
few in the ebase set which could be replaced independently. It is
important that the file be named exactly the same as the old file.
When ebase presents the dialog that it can't find the file, navigate
to the new file to let ebase know where it is.
If contacts_.102 is also showing a problem, however, there are
apparently other errors present. It is likely that your only secure
option at this point is to replace the entire file set with your most
recent backup set, and re-enter done since that time.
--
--
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
---------------------------------------------------------------------
