>1) Is this "non-bug" fixed in VFP9?

No, this has not been fixed in VFP 9.

It has been by design for performance issues. This is annoying because when we receive it, we do not have any information as to know if there is really a corruption or if this message should just be ignored. At first, I was recreating the tags just to avoid taking any chance. But, I haven't done so in the last year because there is never any corruption.

This is also appearing under the VFPOleDb provider. This is based on the engine itself.

As part of the data being accessed under the VFPOleDb provider, you will get more messages about this index corruption thing as this provider generates up to 7 different errors, totally not related, under simultaneous hits when accessing a Web site within such data access.

So, you could try to automate and/or make it easier to recreate the tag in such circumstances. For me, it turned out to be a complete waste of time. We simply ignore this error now. What is really sad about that is this is being taken care by our error handler so when it happens the user might thing there is an error, when there isn't.