>I have a legacy application running on Foxpro 2.6 that is conflicting with a different VFP 5.0 application. They are both sharing the same FoxUser.dbf file. This is a problem as each routine prompts the user to convert the file structure back and forth.
>
>The 5.0 routine does not need to have any resource set so I tried editing the 5.0 Config.fpw file to RESOURCE=OFF
>
>Now I discover that both 2.6 and 5.0 are accessing the same CONFIG.fpw file. What is the command to change where your app looks for the config.pfw file?

Several options:

(1) The command line switch -c can specify the exact fiel to use for the executable.

(2) You can burn a CONFIG.FPW into the application under VFP5

(3) USe RESOURCE=OFF in the CONFIG.FPW, and then do a SET RESOURCE TO in the application; the resource file does not have to be called FOXUSER.DBF. You could have the VFP5 app do a SET RESOURCE TO FOXUSER50, and the FPW app a SET RESOURCE TO FOXUSER26