Rich,

No this behaviour occurs when VFP cannot open the config.fpw (even if it is included in the exe). You can determine this because the main VFP is opened with the title "Microsoft Visual FoxPro" while you set TITLE = Application name in the config.fpw file.

According to a KB article it's due to a error in the path setting in the autoexec.bat. I've experienced that it also occurs due to some other settings in the window environment. I've alway solved this by reinstalling Windows.