>My point is this - the fact that VFP8 reports an error in this scenario is not a VFP8 bug. The error just exposes an old problem that was there for a long, long time. So, don't kill the messenger. :-) The error wasn't added to VFP8 to address this particular problem, it was added to address a real on-disk index corruptions (that should explain the text of the error message). The in-memory index corruption wasn't known issue until we investigated a couple of cases when the error seemed to be reported false positive and confirmed that this is the case. When the issue is known, it is half way to be fixed.

Well, the most important thing for us is to have this resolved. In any good error handling, this is being logged as an error and it stops the application. So, if there is no corruption on disk, which seems to be the case here as even without recreating the tag all is ok after, something need to be fixed. For me, whenever I have this, I have no mechanism to know if there is a real corruption or not. So, in all cases, I have to recreate the tags.