>>Hi,
>>
>>I have one customer with somewhat weird situation of running my VFP 9 application. They have a desktop shortcut that has the target the application executable (e.g. MyApp.exe) and it starts in the application folder (e.g. \\servername\myapplfolder)
>>
>>But when the user double clicks on this shortcut, the application opens with an empty window pointing to need to DO some program. I copied the application file, MyApp.exe, to the same name and extension .fxp - MyApp.fxp. And now user can select this file, MyApp.fxp when prompted to DO a program. And the application works.
>>
>>All other customers do not need to do it; simply starting the MyApp.exe works.
>>
>>Why, do you think, in this case the program is looking for an .FXP file of the same name as the application?
>>
>>TIA
>
>Hi Dmitry,
>
>I lived situation like this years ago with Novell Netware. There was an attribute with Novell, that attribute let you just run executable, you can't copy or open executable with notepad or something else. Foxpro needs to read .EXE file, because you know sources at there and Foxpro should reach .EXE for this issue. Seem your .EXE cannot reach itself after started.I also lived this situation with some .EXE protecters, viruses and file damages.

Thank you, Metin. I am taking the notes and checking all possible causes. The first thing is to disable AV. This is a corporate customer and they have an "approval" process for any little change.