<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">><br>
> You may not have accessed the corrupted part of the index.<br>
<br>
</div>A valid test there, if one were to need one, would be to enter that file<br>
in dclerk, choose the relevant index, go to browse mode, hit down arrow,<br>
and then turn on 'C'ontinuous and let it scan the entire file, correct?<br>
<br>
(Tip: if you try this, do it in an xterm and hide the window; it will<br>
run much faster if it doesn't have to do screen refreshes.)<br>
<br>
Cheers,<br>
-- jra<br>
<span class="HOEnZb"><font color="#888888">--<br>
</font></span></blockquote><div><br>I did that, and it ran through all 500,000+ records with no issue.<br><br>I'm not expecting a solution as I cannot re-create it, it happens maybe once every other week, and it can be a different file and different index. <br>
<br>I just think that when running a report that I know is not 'doing' anything to the indexes, there should be a way to turn off accessing them. Apparently -ro does not do that, and I'm on the latest and greatest filePro version now. <br>
</div></div><br>