Memo file corruptions is the main cause of corruption followed by shift of data corruption. I don't have foxfix and wouldn't be investing in the near future (economics, let the client take care of his own data as he wouldn't be willing to share the cost of saving his data, but if there is some little coding and I can get his data back I don't mind helping <g>).

I was just hoping that there is a way to read memo files, when we get the message memo file is missing or bad. Basic record count errors I have a utility to handle that, but these to remains.

>The memo data is readin fine. I guess I am not sure why you ask about memo fields specifically. Foxfix repairs memo fields (files) also.
>
>Tracy
>
>>>The file has to be readable of course in order for the data to be appended to the newly created table.
>>
>>How about memo data?
>>
>>>Most often, foxfix can fix the table itself on the fly, that is why I like using it. For over 90% of the cases, Foxfix fixes the corrupted table on the fly onsite at the customer's location. Foxfix has a dll you can load in your app that when called will verify the table before opening it in VFP and that is how we do it. I know others like to use SDT...
>>
>>Thanks.