UNC Path to Backend Not Working on Network; Need a Mapped Drive Alternative
Posted on 2006-07-10
Our network is such that UNC paths don't work. I know that they should work. But they really don't, and I have no control over that. (I think it has something to do with our network being a cobbled hybrid of Novell and Microsoft, as they stopped working about that the time that the cobbling began.)
This leaves me with trying to connect to the back end via a mapped drive. Only not all my users have the same mapped drive, and again what drive they have my backend's location mapped to is out of my control.
Is there any way to cycle through the mapped drives via code till the right one is found and then connect? Right now I prompt them to browse to the backend, but I'd like to make it automatic. Just can't figure out how to check for mapped drives.