PRB: Resolving FoxPro "Memo File Is Missing/Invalid" Error

 Last reviewed: October 18, 1996
Article ID: Q94348
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, versions 3.0, 5.0
  • Microsoft FoxPro for MS-DOS, versions 2.0, 2.5, and 2.5a
  • Microsoft FoxPro for Windows, versions 2.5 and 2.5a

SYMPTOMS

When you try to open a table, the error message "Memo File is Missing/Invalid" appears.

RESOLUTION

Copy a valid memo file over the corrupt memo file to access the database again.

NOTE: The original memo field information will be lost unless the valid memo file was an exact backup of the corrupt file. All memo field backup files have an extension of .TBK.

The corrupt memo file will have an .FPT extension, such as OLD.FPT. In the following example, assume NEW.FPT is a valid memo file. To bypass the error message and access the database again, type the following command at the MS- DOS command prompt: 

   copy new.fpt old.fpt
The new memo file being used can be from any database that has a valid memo field associated with it. This allows the database to be opened in FoxPro again.

STATUS

This behavior is by design.

Additional reference words: 5.00 VFoxWin 3.00 FoxDos FoxWin 2.00 2.50 2.50a
repair fix damaged errmsg err msg
KBCategory: kbprg kbprb kb3rdparty
KBSubcategory: FxinteropGeneral

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 18, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.