Apologies if I've already posted this. I remember drafting it a few days ago and can't find any trace of having posted it. I haven't had any replies either so I'm assuming I haven't submitted it.

The problem is the apparently false reporting of a damaged index file.

I'm using my growing vfp version of a long running dos application on exactly the same datafiles still being used by the dos version. In vfp (only) one particular file consistently reports a damaged index with the usual advice to delete it and recreate it. The same file if opened in FP for DOS behaves completely normally with no difficulty whatsoever.

Initially assuming that the windows version of foxpro must have some more sensitive damage detection I recreated a new version of the database from scratch - and got exactly the same response. Even after programmatically recreating the indexes it continued to warn me of the allegedly damaged index.

As I can do everything with this file that I need to I can only assume that this is some kind of vfp bug, possibly a strange quirk arising from its code page registration.

My questions to the panel are
1 - Is this a common problem with a recognised cause (and if so what?)
2 - Do I need to worry about it? (could it cause genuine damage?)

Harry