>>Marco,
>>
>>This problem could be related to the DO ? dialog box problem. In this case VFP cannot find the Config.fpw even if it is included with your exe.
>>
>>The solution to this problem is to check your autoexec.bat for the path setting. It may be so that there is an semicolon ; missing in the path statement.
>>
>>Unfortunate this don't solve the problem in any case, but it's worth a try...
>>
>>If this is not the case, try finding out if reinstalling the client will solve this problem.
>>
>>Please let me know if you found a solution.
>>
>>Regards,
>>
>>Walter
>
>Thanks to you, Walter.
>This computer has an extremely long path-statement. When I overrule the path with a correct shorter one our application starts!

If this is Win9x, you might need to expand the amount of environment space for the system; the long path statement might be getting chopped off because you've run out of string space in the VDM. To do this, add a SHELL= statement to the CONFIG.SYS file, something like:

SHELL=C:\WINDOWS\COMMAND.COM /P/E:xxxxx

where xxxxx is the number of bytes of space to allocate in each VDM for the default environment strings. I'd recommend trying a value in the 2000 range (I believe that the granularity is the nearest 16 byte boundary equal to or greater than the value specified) and working from there.

There's also a limit on the length of the PATH created in the AUTOEXEC.BAT file (I don't remember the exact length, but it's somewhat less than 256 characters); if you really, really need an extremely long and involved DOS path, you can create it in the CONFIG.SYS, but whatever you do, DON'T try to change it later from the AUTOEXEC.BAT or command line, or it'll get truncated again.