Hi Dmitry,

When you "share" a folder with other machines on the network, you can give is the name you want -- it does not have to be the "real" name of the directory underneath. Perhaps that is what happened.

Hank

>Hi,
>
>I have one customer which has my VFP 9 application installed an odd way (in my view). Here is the description of the problem:
>In the application folder (typically \\servername\myappname\) there is a DBF file, SYSDATA.DBF. This file has the actual location of the application (e.g. "\\servername\myappname\")
>When the application starts (in this folder, \\servername\myappname\), there is a feature where the application can change the value stored in the SYSDATA.DBF.
>
>So, this customer, has the desktop shortcut property Start In as:
>

>\\fileshare\orgname\dept\facilities\shared\
>

>The applications starts from this shortcut, no problem.
>I tried, from the application, change the value of the application folder name. Changed it to some bogus name.
>Then, I mapped the drive \\fileshare\orgname\dept\facilities\shared\ to letter Z:
>When I look at the Z: drive, the file SYSDATA.DBF is not changed. It still has the old date and time stamp.
>Yes, when I try to open the application, again, from the desktop shortcut, the application fails - because I changed the application location.
>
>My question is, how do I map the drive \\fileshare\orgname\dept\facilities\shared\ so that I can see the actual file SYSDATA.DBF?
>
>UPDATE. I know - because I installed the application - it is physically installed in the following folder on the server:
>c:\myappname\
>
>So, somehow, they mapped the above folder to \\fileshare\orgname\dept\facilities\shared\ But I don't understand how.