From the FileMaker Forum:
I've been informed that Technical Support has received customer calls exhibiting this behavior. It turns out the index is pointing to a record that no longer exists. Turning the index off and on again does not always fix the problem. Cloning the file and importing from the main file has fixed the remaining customer files. We do not know what is causing the index to point to a non-existent record.
posted March 30, 2010
Please stay honest. This is not a new case, you've known that before.
Huslik GmbH • Bgm.-Widmeier-Str. 42 • 86179 Augsburg • Germany
CEO Winfried Huslik - HRB Augsburg 12386 - VAT-Id. DE127485099
Phone +49 821 565606, Fax +49 821 565001, Email email@example.com
Verify your FileMaker Pro files with FMDiff - http://fmdiff.com
Ok, I did it. I'm just happy today is Saturday and I could close the file down, compress it, reopen it and send the new loaded version up to the server. It seems to have taken care of the issue. So Thank You for pointing out to me a resolve. I hope FM can remedy this one day. In the mean time I know what to do if it happens again.
Just curious, did you Compress it, or import into a Clone ?
> just happy today is Saturday and I could close the file down, compress it, reopen it and send the new loaded version up to the server. It seems to have taken care of the issue
I compressed it.
Sent from my iPhone
Compressing rebuilds the file's block index, but does not re-index fields
It can however fix a multitude of problems
> I compressed it
I chose this route simply because I know how. Until your post I'd not heard of cloning. I'm still not sure how to do it.
Sent from my iPhone
There is one explanation here:
Importing all your records from a backup into an empty "Clone" of the file can also fix many problems
> Until your post I'd not heard of cloning. I'm still not sure how to do it.
The index info actually explains other problems some of my users have been experiencing. The clone should take care of this.
Glad to hear others having this problem. I thought I had a corrupted database. I guess in some ways it is corrupted (index to an empty record) but atleast filemaker has a handle on it.