INFO: Project File Structure Changes in Visual FoxPro 5.0

Last reviewed: March 31, 1997
Article ID: Q155931

The information in this article applies to:

Microsoft Visual FoxPro for Windows, version 5.0

SUMMARY

This article lists the project file structure differences between Visual FoxPro 3.0 and Visual FoxPro 5.0.

MORE INFORMATION

The Visual FoxPro 5.0 project file structure has several new fields. These fields and their definitions are listed below:

   Field Name    Field Description
   ---------------------------------------------------------------------

   ID            Uniquely identifies the object.

   SCCDATA       Information used by Visual FoxPro to enable source
                 code control.

   LOCAL         Specifies whether the object is source code controlled.

                 Type of Record  Setting  Meaning
                 -------------------------------------------------------

                 'H' (Header)    (Empty)  The project is not source code
                                          controlled.

                                 'T'      The project is source code
                                          controlled.

                 All Others      'F'      The object is source code
                                          controlled.

                                 'T'      The object is not source code
                                          controlled.

Keywords : FxotherDochelp kbprg kbusage ssfox ssint VFoxWin
Version : 5.0
Platform : WINDOWS
Issue type : kbinfo

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: March 31, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.