> I tried your config.fpw, and the _STARTUP was ignored. I changed the > _STARTUP program to d:\Temp\startup.prg. When I replace the > c:\VFP\config.fpw with your, it works. This would be OK if I want to > modify my development environment, but I cannot get it to work when I > include the config.fpw in a project and compile it to an EXE. Have you > been able to use this config.fpw in an EXE? If so, what I am doing wrong? Generally, you don't want to include the CONFIG.FPW inside the .EXE. It is the file that is used to direct FoxPro through its initialization, and I wouldn't expect it to work inside the .EXE. There are a number of ways to get FoxPro to see the 'correct' CONFIG.FPW: 1) a command line switch ( -C{file} ) 2) an environment variable ( SET FOXPROWCFG= ) 3) having the file in the file in the current directory These are in order of precedence. I generally prefer options 1 and 2. I have the -C{file} set for the icons that launch VFP.EXE, and I also have the environment variable set (to a different CONFIG.FPW) so that I can test an .EXE that is ready for shipping. At the customers site, I rely on the third option, since they might have FoxPro or something else installed already, and I would rather that their file direct things like the temporary files. /Paul