Recognizing index corruption (was RE: Problem with dreport crashing)

[Jeff Harrison]

--- On Fri, 8/1/08, Chris Sellitto <sellich at guaranteedreturns.com> wrote:
[snip]
> time, this error is triggered by a bad index.
> 
> My question is, is there a utility out there that could be
> run manually,
> that might somehow recognize that an index is bad?  Is it
> even possible,
> and if so, does anyone know how to write one?
> 

I wrote one once.  I don't have it any longer - However, you could easily write one with filepro.  Just have a routine that examines a given index, then builds a new one on the same keys.  Run a report off of each of the indexes - each one outputting to a different file name.  The output should be a 1 line report containing just the pertinent key info.  Then do a diff on the two files.

I'm sure there must be an easier way to do this, but I believe that this is the approach that I used a few years ago when I needed to do this.

Jeff Harrison
jeffaharrison at yahoo.com