How to Use a Custom Configuration File

Last reviewed: June 18, 1996
Article ID: Q152343
The information in this article applies to:
  • Microsoft Visual FoxPro for Macintosh, version 3.0b

SUMMARY

This article describes how to use a custom configuration file. Visual FoxPro determines valid configuration file usage by both filename, format, and type. This allows multiple custom configuration files to exist in one location while having a system default.

MORE INFORMATION

In order to ensure that Visual FoxPro uses a custom configuration file, the following items must be considered:

  1. The custom configuration file must have a type of "FFPM" and a creator of "FOXX." These types can be set by using the FoxTools call FxSetType() or the sample form :sample:tools:setconfig:setconfig.scx.

  2. The default configuration file, CONFIG.FPM, must not exist in either the Visual FoxPro or the System Folder. If it does, it will always be used.

  3. The format of the configuration file must be text and it must adhere syntactically to those conventions and limitations outlined for the default configuration file.

  4. Visual FoxPro must be launched through the custom configuration file either by dropping the custom configuration file onto Visual FoxPro or opening the custom configuration file from the Finder.


Additional reference words: 3.00b VFoxMac
KBCategory: kbenv kbhowto kbwebcontent
KBSubcategory: FxenvConfigfp



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