>Had a problem recently with a VFP5.0 app I built where the tables became corrupt due to our Novell server deciding it wanted to hang. Most of the tables had at least 10-15 records that were completely trashed, as well as the DBC container looking slightly funky.
>
>I went through each of the corrupt tables and reconstructed their structure, then copied the clean data over to them. Things seemed to work ok except for the associated memo file for one of the tables.
>
>Whenever I perform a pack operation on this table it gives me an error message stating:
>
>Memo file is missing or invalid.
>
>Now, when I use the app or browse the table I can see that most of the records still have a memo entry intact and updatable. Adding records causes a error message indicating the uniqueness of the primary index for the table has been compromised, but I cannot locate any duplicate index keys for this table via code or through my own visual scanning. The table appears to be sound, it would appear that the source of my problem is the memo file being completely mangled somehow or the DBC container is got some problems.
>
>Does anyone have any suggestions as to how I can determine exactly what is causing this problem, and also possible ways of cleaning the structures with minimal loss of data? Any help would be extremely appreciated as this has been a live app in constant use by our tech support staff and is currently unusable (gulp...).
>
>Thanks in advance for the assistance...

I believe there is a memo fixing program here in the files section, that is a shareware or demo version.. Give it a try and see what happens.. Rem,ember to first make a backup of your stuff before you try this..