>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 is an old thread but I wanted to update it. For a few customers where this phenomena is happening (requiring to select Applicatin.fxp when starting Application.exe), the temporary solution is to add the Application.fxp as a parameter to the Application.exe in the desktop shortcut property. Therefore the shortcut target says "Application.exe Application.fxp" (where Application is the name of the .EXE). But what is "strange" (at least to me) is that the application runs under the version of the Application.fxp. That is, if I update Application.exe to any new version, the run-time shows the version of Application.fxp (done when copying Application.exe to Application.fxp). Thus, I have to remember, whenever updating the application, to update (re-copy) the Application.fxp.