>Our database won't stop crashing.  I've trouble shooted the problem down
>to the "Replace All Find Fields" Script.  Everytime I run this script the
>database crashes soon thereafter.

Good bit of troubleshooting - small comfort, but it's a good start on 
a solution.

>So essentially I stopped running this
>script, but lately have found that many of our records in the names file
>are not current with the payments file.

That script updates some fields in the names file with current values 
from payments. So, you're right - without running that script, your 
names records go out of date.

>I've been experimenting with
>running the script from a recent start date.  I was successful in going
>from the beginning of our fiscal year (10/01/01) without any problems, but
>when I ran the script from our previous fiscal year (10/01/00) the
>database crashed again.

Again, that's a good piece of troubleshooting. What it looks like to 
me is a damaged record. I suspect that either a payment record from 
the previous fiscal year or a names record is damaged, so when 
FileMaker attempts to copy the data from payments and write it into 
the Fast Find Fields in names, it crashes. The other possibility is 
that the update script is damaged, although if you can run some part 
of the records without a problem, that's less likely Maybe someone 
who knows more about what goes on inside FileMaker can comment.

Walt's suggestion is basically right - you will need to abandon this 
file set, since it has been crashed repeatedly. The problem is that 
if a record is damaged, when you migrate the records to a new file 
set you'll take the damage with you.

I'm not entirely sure how to find the damaged record, but I would try 
first exporting all the fields in all the records from both the 
payments file and the names file. If FileMaker chokes during the 
export, you might be able to identify the record it stopped on. If 
the export doesn't fail, then move the data to a new file set and try 
your update scripts again.

I'm sure this sounds like a lot of work, but I'm quite sure there is 
no shortcut such as replacing only the damaged script, or even the 
damaged file. The ebase files are interlinked in a way that makes 
that impossible.
-- 
--
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