Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Mapped Drives not recognized in Windows 10
Message
From
02/04/2016 07:05:36
 
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows 10
Network:
Windows Server 2012 R2
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01634105
Message ID:
01634186
Views:
69
>>>>>>>>>Have a VFP Application which does a File Copy from a mapped Drive. Works fine in XP, Win7 & Win8.
>>>>>>>>>In Windows 10 am getting a File Not Found Error even though the Mapped Drive and File are visible in Windows Explorer.
>>>>>>>>
>>>>>>>>If you run the app in Windows 7 compatibility mode (but make no other changes) do you still get the error?
>>>>>>>
>>>>>>>Yes
>>>>>>
>>>>>>On the Wndows 10 machine, can you read/write files from the windows explorer in that mapped drive and folder ?? It sounds like a permissions problem to me.
>>>>>Yes can do a File Copy directly in Windows Explorer. The FoxPro App doesn't see the Network Folder.
>>>>>Also - this is a Laptop running a Wireless connection
>>>>
>>>>Is the Foxpro app trying to do a read, or write, or copy, or delete? Or some combination of these???
>>>
>>>Trying to do a Copy. CD to the Mapped Drive doesn't work either - think this is a Windows 10 Bug (or as Microsoft likes to say not a Bug but a Feature).
...
>Am running a program that copies and registers files from a Subfolder on a mapped Drive. Can manually copy via Windows Explorer. Permissions look OK. Even a CD line doesn't recognize the Mapped Drive as a Letter.

"CD line" from vfp run/! or from separate Cmd-Window established without vfp involvement ? If second, as Copy from Explorer works, how about Copy from such a Cmd ? Did you try path/fileselector GUI elements in vfp, like Getfile() or mscomdlg.commondialog ?

//upd:
as a patchwork 1 (not recommended) "solution" try to set the default dir to the invisible path in a .lnk
as a patchwork 2 (not recommended) "solution" look up the object model of IE, esp. the interfaces it "also" implements. I do remember that IE sports the IPersist* interfaces, perhaps a method in this or other IE interfaces can get a hold to that dir similar to Windows Explorer (try out in IE manually first).

If something after "upd" works, think of it as emergency patching needing to be pruned from the code base ASAP and stay on the ball to find a better solution
;-)
Previous
Reply
Map
View

Click here to load this message in the networking platform