>>>>>Hi,
>>>>>
>>>>>I have been having this situation with a customer for a long time but finally would like to address it. Maybe someone can see what I am missing.
>>>>>
>>>>>VFP9 application installed on drive E: in folder MyApp. The name of the server is MyApp (actually the same as the application; for whatever reason they named it so). The folder E:\MyApp is shared and in the Sharing properties of this folder I see it as shared with Network Path:
>>>>>\\MyApp\MyApp.
>>>>>
>>>>>VFP9 application has a configuration file that stores the application folder name (\\MyApp\MyApp\) and when the app starts it looks for certain files in the application folder (MyApp) just to be sure that configuration is correct. And everything works for the custom. That is, they use the application and NO problem for them.
>>>>>
>>>>>But, when I RDP to this server and start the application (in the folder MyApp) I get message that the folders are not specified. So for me, connected to the server via RDP (and I have admin password), the VFP9 does not find folder \\MyApp\MyApp. What could be causing this problem? Any suggestions? TIA.
>>>>
>>>>
>>>>Does the same thing happen if you remote in using DameWare or VLC or some other client?
>>>
>>>I have only remote via VPN to the customer network and then Windows Remote Desktop. So I have not tried to remote any other way.
>>
>>
>>Try to remote in via RDP, and then use RDP to launch TeamViewer and connect that way and see if you can run the app over TeamViewer. I'm guessing you will, which suggests your VPN connection is intercepting the \\MyApp\MyApp\ request and somehow trying to route it.
>
>I don't know what TeamViewer is (will have to Google for it). I see what you are saying about VPN connection being intercepted I have never experienced such thing. And I connect via VPN to many other customers but no issue. I think the problem has something to do with how the folder MyApp is being shared and access rights. But I can't figure out what is wrong.
>Thank you.


That shouldn't be too hard to test, right? Just browse to the folder once you're logged in. Or write a test app whose sole purpose is to try to access that particular folder, and run that test app. AT least that would isolate single-instance app issues, and possibly make it a VFP-in-general or rights issue.