PRB: "Invalid File Format" with dBASE IV Screen File

Last reviewed: June 28, 1995
Article ID: Q112318
The information in this article applies to:
  • Microsoft FoxPro for Windows, version 2.6
  • Microsoft FoxPro for MS-DOS, version 2.6

SYMPTOMS

When you issue the MODIFY SCREEN <filename> command on a dBASE IV screen file, the following error message occurs:

   Invalid file format. If this is a dBASE file, use the Catalog Manager.

RESOLUTION

To work around this problem, do one of the following:

  • From the Run menu, choose Convert dBASE Files, and then convert the .SCR file to an .SCX file.

    -or-

  • Run the Catalog Manager and add the dBASE screen to the catalog. The file will automatically be converted when you choose the Modify or Run button.

MORE INFORMATION

NOTE: The error message does not mention that you can migrate the screen to FoxPro by choosing Convert dBASE Files from the Run menu or by running the Catalog Manager and adding the dBASE screen to the catalog.

Steps to Reproduce Behavior

  1. In the current directory, create a dBASE IV screen file named ADDBOOK.SCR.

  2. In the Command window, issue the following command:

          SET COMPATIBLE DB4
    

  3. In the Command window, issue one of the following commands:

          MODIFY SCREEN addbook.scr
    

          -or-
    

          MODIFY SCREEN addbook
    


Additional reference words: FoxDos FoxWin 2.60 errmsg err msg
KBCategory: kbprg kberrmsg kbprb
KBSubcategory: FxinteropDbase


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: June 28, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.