Lately, I've had several cases of indexes going bad in hosted DBs. That is, I do a search on a field and the results don't correspond to the data that's stored/displayed in the field. There may be few or no records found when I expect thousands, or there may be no records when I search for >0 in a field which has data for most records. The solution is always toggling indexing on and off, but if the field I'm searching is a calc, the actual problem might be somewhere down the line, and tracking down which field needs reindexing can be cumbersome.
Is there some way to force FMP to recalculate all the indexes? Or is there at least some way of detecting this problem that doesn't rely essentially on chance?