No, you can put those lines in your main .PRG program.

HI peter,

As Fred pointed out, that syntax would run in any VFP code, prg,
method, whatever.

As for the config.fpw option, syntax is different there - for example,
you can set the Title in a config.fpw
   title = my project
(w/o quotes).
But I think you can not change the icon that way.

OTOH, the actual advantage of a config.fpw is that it is evaluated
very early, i.e. long before your "main.prg" code jumps in and also
before _screen gets visible and foxuser.* is created.
So IMO it's useful to do only a few things there at runtime, maybe
just
   screen=off
   resource=off

That way (you won't get a useless resource file on a customer's box
and) _screen won't be visible until you tell it to be, i.e.  later in your
code, probably after having designed _screen to meet your specs.
   * "main" startup pseudo code
   && _screen is invisible yet by config.fpw line
   With _screen
       .Icon = 'your.picture'
       .Title = "xy"
       && .BackgroundColor = RGB(255,0,0) &&etc.. And finally:
       .Visible = .T. && m.yourChoice, depending on mainForm.ShowWindow
   EndWith

As for the file name, if you do want to use a "config.fpw" file, you can
use any name and use the -C commandline switch,
e.g. call it "yourConfig.file" and have a desktop shortcut pointing to
   x:\theFolder\your.exe -CyourConfig.File

or, with Windows' "long" file/path names
   "x:\some folder\extended name.exe" -CyourConfig.file

You wouldn't need a -C parameter by using the default name.
(If you include a config.fpw via project manager, you don't need
to ship it separately)

hth
-Stefan

Why not just rename the icon, and the flyover text so that you don't get
them confused?