Map web folder (WebDav) from code

I try to map a WebDav folder from vb6 using code attached (in WinXp SP2) ... but fail with Error 67 ERROR_BAD_NET_NAME

When i try to map using Windows wizard (Add network place wizard) everything it's Ok...but i want to map from code...
I try every suggestion from here :
http://ulihansen.kicks-ass.net/aero/webdav/index.html .. but not work

Please Help,

i try also to use this:
http://www.vbforums.com/showpost.php...7&postcount=10...same error

This approach uses the WebDAV MiniRedirector, which is broken in various ways on different OSs:

http://greenbytes.de/tech/webdav/web...ctor-list.html

It is most stable in Vista and later, and will probably never be fixed for XP.

For embedded use in an application you'd want a reliable 3rd party WebDAV client library. If you require a redirector (allowing drive letter mapping) you may need a 3rd party product, but these require installation and rebooting since they involve device drivers.

There is also the Web Folder Client. The only API I'm aware of for that was based on ADO, but this was broken in Vista and later by an Office patch. I'm not aware that it offers redirection, so programs can't just open files via this approach.


You can write your own WebDAV client in VB6 based on WinHttpRequest or XmlHttpRequest. This can simple to difficult depending on the level of functionality you need.

However this presumes embedded use: the code must implement I/O, rename, etc. operations as internal calls. It does not map a drive letter to permit standard file I/O operations like VB6's Kill, Open, Get, etc. or access by a "shelled" program or batch file. This is the same as when using a 3rd party ActiveX library.

Quote:

---

Originally Posted by dilettante

This approach uses the WebDAV MiniRedirector, which is broken in various ways on different OSs

---

Thank you very mutch for clarification.

There is a hack that can get around this error in XP, and it can apply to some Vista Service Pack levels too:

http://www.yggenyk.dk/wiki/How_to_fi..._XP_SP2_client

This is a registry tweak that is also described in the other article I linked to above in post #2.

Note that this only addresses one of the possible issues in XP though, and might not cure the error you are seeing.