>>>>>>>Attach a net volume.
>>>>>>>Execute VFP in administrator mode.
>>>>>>>GETFILE()
>>>>>>>
>>>>>>>VFP doesn't see the net volume.
>>>>>>>
>>>>>>>Work on Windows 7.
>>>>>>>A windows 10 bug ?
>>>>>>
>>>>>>I have no idea what the net volume is. Do you mean a mapped drive? Use UNC paths, this works at least with 8.1. No idea of 10, will skip it.
>>>>>
>>>>>yes, mapped drive.
>>>>>
>>>>>>Have you tested sednas getfile equivalent?
>>>>>
>>>>>Getfile() is an example. The whole process does not see the mapped drives
>>>>
>>>>Sedna uses an other way / interface to query the file system. (AKA newer style). That's the reson for my question.
>>>>
>>>>if you directly enter the drive letter via CD, will it fail?
>>>>
>>>>Not that I can help, it's just the POV I see.
>>>
>>>sure CD and every filesystem functions.
>>
>>I agree that the File dialogs should show what you can adress on commandline level.
>>
>>But then mapped drives. Why? It's outdated for decades. There is UNC for decades?
>
>outdated ?
>who decides that something is outdated?
>If it is useful it is never outdated.

It was a quirk from start (as all the dos drive letters).
All this fancy mapping one need to do, not very reliable - just enter a UNC path and you are done. Mapped drives only add a level more to fail. (IMHO)

I do UNC paths as default and if customer decides to map a drive - I do not offer support for M$ OSes. :)
Not one is using that, after they have learned that there is simply no need to do it.

;)