>>>A number of times we have built an exe with the top line in the config being
>>>PATH = DATA;GRAPHICS;REPORTS
>>>
>>>We then create a short cut to the project.
>>>
>>>The start in is in the project root. We use the -c switch to give the name of the config. We have tried without the path and also fully pathed. For some reason the path is not taking. Only by adding a path statement in the code at the beginning of the program does the pathing work.

We fought with config.fpw for a while before finding the documented search path. This is from memory, so you may wish to check this:

1) config.fpw in the application directory
2) first config.fpw found in the DOS PATH. (That's right, the DOS path!)
3) config.fpw embedded in the application
4) named configuration file (using -c) on the command line starting the application.

The Fox path is never consulted to find the config file, since the config file is executed before the application begins. The reason that the embedded config.fpw does not take precedence is so that you can use different configurations for each copy of the application that you distribute. But in that case, it must be named "config.fpw" and must be in the application directory to be successful.