>>>>I have an vfp.5 exe located on a win-nt server along with the required dlls. When excuting this exe from a client machine, the open dialog box appears, once you select all files, then the exe, the program runs fine on the users machine. Why is the open dialog box appearing? I appreciate any help on this.
>>>>
>>>>Thanks
>>>>Tom
>>>Sounds like your .exe is looking for a file (mnx, fxp, etc) that it is trying to run. When the app does not find it, it prompts you for the location.
>>>
>>>Wayne
>>
>>Wanye thanks for the speedy response. I failed to mention that on some clients
>>the program is working properly. Also, to test I put as the 1st line of the m.extapp the command _Screen.Caption ="Test". The dialog appears before the caption is changed.
>>It has me baffled
>>Tom
>
>
>Do you have any references to anything in a config.fpw file? I don't know what, but that is referenced before your app starts.
>
>Wayne


Hi Wayne.
I found the reason, and you are correct about the config.fpw being involved. I'm including what we found and 2 possible solutions in case anyone else runs
into this problem. The Problem is detailed in MSDN Article ID# Q163801.

The client machines had a path statement in the autoexecute.bat with a semi-colon missing between two differnt directories statements. When VFP loads it 1st searches for the config.fpw along the path. When it encounters an invalid path it bails out and presents the "DO" dialog. Specifing the config file and location in a comand line switch i.e.[do c:\anypro.exe -cC:\config.fpw] will not fix this problem. I found two ways that work. One is to correct the path error. This works great and is the right way to go, but with over 400 machines and no two autoexec.bats the same, was not especially appealing. What we did is create a bat file to map the server, reset the path and then execute the exe. It works fine until we can get around to correcting all of the machines path statements.

Thanks again for the assistance.
Tom