While you're probably right in dismissing them, I do want to point out that:
1) the specific instance cited refers to a specific repro procedure. There could well be other conditions, not so easily reproducible, that cause the same problem. For instance, an old bug addressed in VFP8 had to do with "corrupt" tables and the dropping/loss of records without error. The single reproducible instance involved TRANSACTIONS. But there have been reports of the same situation happening outside the TRANSACTION environment but they have not been reproduced.
2) The fix can fix other apparently unrelated problems.

Anyway, it might be worthwhile to convert the specific app to SP1 first just to find out.

cheers

>Thanks Jim,
>-see in text below...
>
>>You don't say what version of VFP Doru, but there is the following fix in SP1 of VFP8 that may be relevant:
>
>Version is VFP8, SP1 we have it on development machines but not on production WS.
>
>>"Engine - After calling TABLEUPDATE( ) and ROLLBACK command in local view, "Index does not match the table" error occurs on GOTO TOP command.
>>".
>>Another probably less relevant was: "Engine - "Index does not match the table...(Error 114)" occurs when calling TABLEUPDATE( ) function on a table-buffered cursor with buffered changes and using REINDEX command.".
>>
>
>This is on a free table, so no transactions, no ROLLBACK, and we never use REINDEX.
>
>>good luck
>
>That could help, but we didn't have much so far :(