How to Create and Use View Files

 Last reviewed: June 27, 1995
Article ID: Q93351
The information in this article applies to:
  • Microsoft FoxPro for MS-DOS, versions 2.0, 2.5, 2.5a, 2.5b, and 2.6
  • Microsoft FoxPro for Windows, versions 2.5, 2.5a, 2.5b, and 2.6

SUMMARY

The CREATE VIEW command creates a new view file that contains information about the FoxPro environment. SET VIEW restores the environment to that saved in a view file. A view file created by the CREATE VIEW command has the .VUE extension.

NOTE: In all versions except FoxPro 2.0 for MS-DOS, the DEFAULT path is not restored.

MORE INFORMATION

CREATE VIEW builds a new view file that contains the following information:

  • Established relations between open database files
  • Fields in the SET FIELDS list
  • Database, index, alternate, and format files open in each of the 225 work areas (NOTE: For FoxPro 2.0 and the Standard (16-bit) versions of FoxPro 2.5 and later, the number of work areas is 25.)
  • Filters in effect for open databases
  • ON/OFF switch settings
  • DEFAULT and PATH settings
  • Procedure file settings
  • SET SKIP status
  • Status bar state (ON or OFF)
  • Current resource file
  • Current Help file

View files can be a useful tool during application debugging and testing. For example, during the debugging process, if you save the environment to a view file and then perform your testing, you can restore the environment to its original state before continuing program execution.

Additional reference words: FoxDos FoxWin 2.00 2.50 2.50a 2.5b 2.60
KBCategory: kbprg
KBSubcategory: FxenvFoxuser

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