HumblePie

I speak Spanish but am English. Any good?

I have done this using either the auto enter calc or validate by calculation, triggering a script (using Dacons scriptfire, Waves events, Troi activator etc...) which sets the field. Any of the fields referenced by the field in question would need to have this in their definition. You could even have an uninexed calc with the same kind of thing, setting a counterpart indexed field whevever its value changes? Come to think of it, that would be better.

The only way to keep values in find mode is to set globals , either manually or through a script step. Global calculations and locally stored fileds will all disappear. Hope, but doubt, this helps.

I have found that going to the last known uncorrupted backup, creating a clone and re-importing (over a weekend probably) is the only way to be absolutely sure. A less extreme solution is to recover BEFORE being prompted. This rebuilds all indexes just for starters. But appears to do other good besides. Don't bother with file maintenance if you are uncertain as to the integrity of the file, by the way. In my opinion, corruptions are rather better diguised in the .fp7 format. You can continue for a while before they rear their ugly head. They can be caused by any complex relational process like a non-indexed search or calculation, so it is REALLY important to be sure of all of your TOs and predicates, that they are sound and indeed necessary. Is this solution still being "developed" from time to time as well or is it simply being "used"?