2 of 2 people found this helpful
Yes, but you can also use advanced recover options to produce a new copy of the file where the only change is all indexes rebuilt:
select: "copy file blocks as is" and "rebuild indexes now".
import all data into a clone of the file.
Open Manage Database and use field options to turn off indexing on a selected field. Click OK to close Manage Database, then return to Manage Database to turn indexing back on.
As already explained, you can use Manage Database to set Indexing to "None", and leave "Automatically create indexes as needed" checked. FileMaker will then rebuild the Index
The problem here is our tools. Recover is a great utility, built by Geeks, with a log not readable by humans. Most "Real" databases ( e.g. SQL ) have a simple option to verify an index
It is also odd that Recover would report no "Problems", when it appears your index was scrambled ( check the Recover Log for any "difference" other than zero )
> I decided the script was just fine, thank you, and ran a "recover." It did not turn up problems but did rebuild indexes and solved the problem.