>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

This issue has been resolved and I wanted to share with you how (in case anybody come across a similar situation). The folder where the application was installed was corrupted (general term as we don't know exactly how). I could not get into the Share properties of the folder, neither could the customer IT admin person. So last night he shutdown the share of this folder. Then I created a new folder and copied all files from the old/corrupted folder. He then set the share of the newly created folder under that same name as was the old share. And everything works without user being prompted for .FXP file and without the need for having the .FXP file as a parameter in the desktop shortcut properties.