>I am using frmGenLoader from the VB Script loader. Currently, all of the testing is on a local basis. I can enter the executable name, local directory and remote directory in the textboxes and generate a VBS which works.
>
>However, when I try to enter the config file name, the entry "-cconfig.fpw" in the txtEXEParms textbox, I generate a VBS file which gives me a "file not found" error when executed. The file config.fpw does exist in both the local and remote directories.
>
>I have tried a number of different approaches in txtEXEParms without success. Any suggestions?
>
>By the way, John replied and is looking into this as well.

As I said before, it sounds like a problem involving an LFN with embedded spaces, such as "C:\Program Files\My Application\Myapp.exe". The WSH would be interpreting the items after the first spaces as parameters. This would explain the behavior you're seeing. When I deploy an application, it's directly off the root directory and there are no spaces. Here's a sample from a script that's currently in production.

Set oShell = CreateObject("WScript.Shell")
cParameters = " -cC:\VFPLOCAL\EFF_RPTS.fpw"
cStem = "EFF_RPTS"
cExe = cStem & ".exe"
cLocal = "C:\VFPLOCAL\"
oShell.Run(cLocal & cExe & cParameters)

One of the reasons that I know that everything works correctly is that the application checks and makes sure that the configuration file is correct or it aborts.

If you could post the generated code, it would be a help.