PRB: Converted 2.x Screen Can Not Be Opened in Prior Versions

Last reviewed: April 30, 1996
Article ID: Q129014
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, version 3.0
  • Microsoft FoxPro for Windows, version 2.6a

SYMPTOMS

When trying to open a screen file in FoxPro for Windows version 2.x that has been modified in Visual FoxPro version 3.0, you get the error message "Not a table/DBF."

CAUSE

When you open a version 2.x screen file in Visual FoxPro, the screen converter creates a new screen file by the same name with a modified structure. Previous versions of FoxPro will not recognize the modified structure, so the converter saves the previous version screen file with a .S2X extension.

WORKAROUND

Rename the version 3.0 .SCX and .SCT files to something other than what they are currently. Then rename the .S2X and .S2T files to .SCX and .SCT.

NOTE: The converter will always make backups of the previous versions of your screen files, so you may want to store all your newly converted files in a separate directory for easier file maintenance. If screens are converted when converting a project, the original versions will be placed in a directory called OLDn where n is an integer between 1 and 99. The converted project and converted reports will also be placed in this subdirectory.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create a new screen in FoxPro version 2.x for Windows.

  2. Save and close the new screen.

  3. Open and convert the screen in Visual FoxPro.

  4. Save changes; then close the form in Visual FoxPro.

  5. Try to open the screen in FoxPro version 2.x for Windows.


Additional reference words: 2.60a 3.00 VFoxWin
KBCategory: kbprg kbprb
KBSubcategory: FxprgGeneral


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: April 30, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.