Hi Bernhart,

The following might be helpful:
http://fox.wikis.com/wc.dll?Wiki~UDF_FixRecCount

You seem to have a very reproducible problem here. I wonder if it can be 'compressed' into code suitable as "repro code" for a VFP Bug Report (that you could post here too)?

The would be specifically GREAT **if** the situation does NOT involve TRANSACTIONs - MS has a repro for that but none for non-TRANSACTION processing.

One other person who was persistently getting this error in a production application got relief when he moved his tables to a new HD. The guess there was that there may have been something a bit flaky in his original HD, which he knew to be an older one.

As regards SDT, I don't know the answer.

good luck
Jim

>Hello Sergey,
>
>My setting for "SET TABLEVALIDATE " is 3.
>I tested 7 and 15 but I always have Meta.oSDTMgr.OpenAllTables(F., F., F.) always returns .T.
>and It does not detect the error 2091.
>Table "name" has become corrupted. The table will need to be repaired before using again. (Error 2091)
>
>Stonefield can it repair the error 2091 ?
>How to make to repair this table ?
>
>Bernhart