>>>I tried all the things suggested! Just wondering why they do not work. I thought the Config.fpw should allow control of each workstation as needed. Any other suggestions would be appreciated.
>>
>>There's the question of the folder in which your app starts, because the config.fpw will be taken from that folder. If you don't specify the folder, there's no way to know where your app will be launched - the location may depend on the version of the OS, whether it's launched as a service or as an in-process dll etc. Check set("directory") (undocumented but works) to see where the app is running, and try to put the config.fpw there.
>
>IMO explicit call on the command line is ***much*** better - for those afraid of that black square the option of multiple, nicely named shortcuts with explicit config file is a nice solution ;-)

And a maintenance headache. Can you imagine explaining to some IT moron what exactly to put into a shortcut, pointing to an UNC on the server, which would then have to be replicated across dozens of workstations?

Though, I've seen this being circumvented by having them make just a shortcut to the launcher, and the launcher would then launch the app with the complete line, including fullpath to the config.fpw. And that worked nicely.