PRB: EXE with Included CONFIG.FPW Does Not Allow -C Option

MORE INFORMATION

Steps to Reproduce Behavior

1. Create a new project, TEST.PJX.
2. Add a main program, TEST.PRG, with the following contents:

      =Messagebox("Main program!")
   						

3. Create a CONFIG.FPW file with the following contents:

      TITLE=Built in CONFIG was used
   						

4. Add the CONFIG.FPW file to the project as a Text File. It will be marked Included by default.
5. Build an executable, TEST.EXE.
6. Create an alternate config file, OTHER.FPW, with the following contents:

      TITLE=Alternate CONFIG
   						

7. From the Win95 RUN menu, execute:

   C:\<directory with EXE>\TEST.EXE -cOTHER.FPW

Despite the -c to override the built-in CONFIG file, the main Visual FoxPro window appears with the title of "Built in CONFIG was used," demonstrating that the built-in CONFIG.FPW file was used rather than OTHER.FPW.

There are two methods to work around the problem in the above example.

Method 1:

Under step 4 above, add the following:

   4a. In the Project Manager, right-click on the Config file and select
       Exclude.
				

Method 2:

Change step 3 above to read:

1. Create a MYCONFIG.FPW file with the following contents:

         TITLE=Built in CONFIG was used
   						

Change step 4 above to read:

1. Add the MYCONFIG.FPW file to the project as a Text File. It will be marked Included by default.

Now the built-in configuration file, MYCONFIG.FPW, can be utilized only by specifying the configuration file, such as C:\<directory with EXE>\TEST.EXE -cMYCONFIG.FPW. Use of -c will cause no configuration file to be used, and -cOTHER.FPW will allow OTHER.FPW to be used.