Unstored Fields Indexed?

[Courtney]

I compared my live file with the "recovered" file, where FileMaker made changes to field options in 3 of my fields. No other errors were noted in my recovery process.

The 3 fields that were changed are unstored calculations, and for some reason they are all set as "indexed" in my live file. The recovery process removed that indexing.

Any ideas on what might have caused my fields to become indexed in the first place when they are unstored calculations? I can't fix it in my live files, because clicking the indexing box is not even an option on an unstored field.

[James Gill]

As long as the referenced fields aren't unstored or related via a table occurrence, you should be able to switch between stored and unstored at will...

[Courtney]

They are all 3 based on fields in a related table.