A little more background - Windows File Explorer itself does not support it yet. The result would be our mapped drive client could not display virtual drives in File Explorer exceeding 260 characters.
https://superuser.com/questions/320801/alternative-to-windows-explorer-for-long-path-names/320954
One possible work around would be to create shares that start deeper on the file server to shorten the path.
i was not thinking about the mapped client because we do not use it, just the web interface.
Richard L Lanard
it would be great if your program could use long paths over 260 or the unicode version of the API
https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/
The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters. This type of path is composed of components separated by backslashes, each up to the value returned in the lpMaximumComponentLength parameter of the GetVolumeInformation function (this value is commonly 255 characters). To specify an extended-length path, use the "\\?\" prefix. For example, "\\?\D:\very long path"
thanks,
1 person likes this idea