Soounds like a restore from backup is needed. FoxPro Memo files are very fragile when it comes to computers going down right in the middle of writting to them. There are a few utilities you might try that fix memo files, but you really have to know your data before and after the crash to ensure that the fixes work. See the download section for these utilities to fix broken memo files.

>My client had a problem late Monday (4/14) which caused their Win2K server with a 5 disk raid array to "lock up" -- in their words. This ocurred during the monthly close procedure of a VFP 6 app that uses 2.x style tables. During the close process, completed records are moved to history, deleted from the active tables, and the active tables are then packed. When the server had been rebooted, a considerable amount of data was found to be missing but it doesn't follow any typical pattern.
>
>The history files are missing all records from mid-December 2002 on, not just the data that should have been appended during yesterday's close. This is about 3 month's worth of information. The active tables are missing all of the records that would have gone to history during the March close as expected. But, they are also missing the majority of the data entered into memo fields since last Thursday (4/11). Even memo fields with data going back several weeks or months only seem to be missing the current notes. All of the new records entered during this period are still there; only the memo data is missing.
>
>Another user was logged in at the time of the problem. She was updating an existing Excel spreadsheet when her workstation locked due to the server problem. The Excel file is entirely missing from the server.
>
>Any ideas what happened?