Config.fpw Sample

Sample 1

PATH = C:\VMP2005\XLIB\; C:\AE\DATA; C:\AE\DvStuff; C:\VMP2005\GRAPHICS\XP\; C:\PROGRAM FILES\MICROSOFT VISUAL FOXPRO 9; C:\MF; C:\FoxUnit; C:\AE\Tests; C:\Stonefield\SfCommon; C:\Stonefield\SDT; C:\Stonefield\SDT\Source; C:\Stonefield\SDT\DBCX; C:\AE\DATA\Production\; CategoryManager STATUS BAR = ON CLOCK = STATUS EXCLUSIVE = OFF DELETED = ON MULTILOCKS = ON _Builder = "C:\VMP2005\XLIB\XXBUILDER.PRG" _GenMenu = "C:\VMP2005\XLIB\GenMenuX.PRG" Command = DO SetupStuff IN "C:\VMP2005\XLIB\a.prg"

Sample 2 Will help to load your applcation faster

* * production CONFIG(uration).FPW file intended to be built * into your distributed .APP/.EXE * * the following items reduce initial load time: * _Browser = SPACE(0) _Builder = SPACE(0) _Converter = SPACE(0) _Coverage = SPACE(0) _GenMenu = SPACE(0) _GenGraph = SPACE(0) _GenHTML = SPACE(0) _GenXTab = SPACE(0) *!* _ReportOutput = 'C:\Program Files\Microsoft Visual FoxPro 9\ReportOutput.App' _ReportOutput = ReportOutput.App _SCCText = SPACE(0) _SpellChk = SPACE(0) _Transport = SPACE(0) _Wizard = SPACE(0) * * these are new to VFP 7.0, but won't cause a problem in VFP 6.0: * _CodeSense = SPACE(0) _FoxCode = SPACE(0) _FoxTask = SPACE(0) _ObjectBrowser = SPACE(0) _TaskList = SPACE(0) * * we STRONGLY recommend that distributed apps never use a resource file: * RESOURCE = OFF * add other settings as desired, like a PATH statement * PATH = Data; Data\Production\ * Depending on where the data resides, you may instead: * 1- Specify a network path above * 2- Not specify the path here, but rather in the application itself, somewhere like: * - The ??MAIN.PRG main calling program, before calling XXFWMAIN.PRG * - The CustomSetup local procedure in the ??MAIN.PRG main calling program * - Remove the CustomSetup local procedure in ??MAIN.PRG, and create a standalone CustomSetup.PRG * - The app-specific oApp.SetupHook1() method (may be too late in some scenarios)


* VMP Users
* these SETtings are expected/assumed by XXFWMAIN.PRG, and recommended:

Specifying an External Configuration File

You can use an external configuration file in addition to an internal configuration file in circumstances where you need to configure settings separately. For example, setting SCREEN=OFF should be performed in an internal configuration file.

You can set Visual FoxPro to read an external configuration file following an internal configuration file by using the new ALLOWEXTERNAL directive in the internal configuration file. When you include the setting ALLOWEXTERNAL=ON in the internal configuration file, Visual FoxPro searches for an external configuration file, usually Config.fpw, and reads its settings. You can also specify a different configuration file using the -C command-line switch when starting Visual FoxPro.

To read an external configuration file after an internal one
In the internal configuration file, set the special term ALLOWEXTERNAL to on.


When you start your program, either specify a second configuration file using the -C command-line switch or have a second configuration file in the default program path.

For more information about command-line switches, see How to: Use Command-Line Options When Starting Visual FoxPro.

The settings in an external configuration file take precedence over those in the internal configuration file, if duplicate settings exist, because the external configuration file is read after the internal file. Visual FoxPro does not begin initialization until it reads both files.

If you want to specify the configuration file as read-only, place the file in your project and mark it as Included. If you want to specify that the file can be modified, place the file in your project and mark it as Excluded. You can then distribute the file separately with your application or executable file. By convention, configuration files use the .fpw extension.

  Last Updated: 07/06/10 | © Mesquite Information Technologies, Inc., 2012