PC SOFT

FORUMS PROFESSIONNELS
WINDEV, WEBDEV et WINDEV Mobile

Accueil  |  Messages récents  | Connexion  |   | Français  FR
Accueil → WINDEV 2024 → [WD20] fSelect issue with Windows 10 and network drives
[WD20] fSelect issue with Windows 10 and network drives
Débuté par Yaku, 23 juin 2017 14:16 - 3 réponses
#1
Posté le 23 juin 2017 - 14:16
Hi everyone,
I'm having some trouble with the function fSelect in one of my programs.
That program has The "UAC manifest" included, with the requirement of admin privileges.
If I execute it on a Windows 7 machine, no problem whatsoever, but starting the same program on Windows 10, it doesn't find network drives.

The documentation for fSelect says that fSelect has some problems with network drives in Windows Vista and later... but it works on Windows 7.
How can I solve this?

TIA
#2
Posté le 23 juin 2017 - 16:06
Hi

There is a registry key for that... You'll have to google to find it, as I do NOT remember it, but it basically authorize (or not) the network access...

Be aware that even if it is set correctly, a windows update CAN reset it to NOT authorized without your knowledge.

However, as your application has admin privilege, you can start by forcing the value in the registry.

Best regards
#3
Posté le 23 juin 2017 - 16:21
Hi

I have no issue of using fSelect in w10-64bit with mapped network driver
GL,H:,I:,... and even with "\\windowServer\path1\subPath\myFile.txt" and
the filePick does popup right away.

I guess it must be domainUserRight issue in your windows server, pls check it out.

HTH

King
#4
Posté le 23 juin 2017 - 18:24
Hi everyone,
Thanks for your replies, i will surely look for those values.
→ Revenir à WINDEV 2024