Thanks Al,
I have checked them out, no luck. Found out what the problem was, the corrupt records belong to one operator, she was using an old win98 workstation that was having parity errors on a regualr basis for a couple of years, the boss wouldn't get it fixed/replaced.

It is only now that the companies regulatory compliance depends on the data that he is looking at fixing it, they have been fully aware of the problem for some time.

My next step is to get an order before any further works, the boss is one of the tightest p...ks I have ever come across.

>There are some repair utilities listed in the downloads section here: Main Page...Downloads...search for "repair"
>
>There is also FoxFix: http://www.hallogram.com/foxfix/
>
>Don't know if you've had a chance to try any of these. Might save you re-inventing the wheel.
>
>>No, the corruption goes back beyond the last backup. Looks like I will have write a routine that will allow the operators to see the data and then they can decide what belong to what.
>>
>>BTW This is not our app, I have been called in to do the repair. This is another example of why we stopped using VFP memos years ago.
>>
>>>>Hi,
>>>> I am trying to repair a corrupt dbf/memo file that contains critical data. The problem I am having is dbf records with cross linked memo block pointers, i.e. record 10000 points to memo block 100000 and record 20000 also points to memo block 100000, which record belongs to the memo block.
>>>>
>>>>Any body have any ideas, as there are several thousand records cross linked and without a backlink in the memo file pointing back to the record it belongs to, it is difficult to work out whats what, especially when you know how the memos work.
>>>
>>>Do you have any non-corrupt backups? Even if they're relatively old, they might give you enough information to be able to resolve some or most of the cross links.