If this setup had worked as described in Windows it would have solved a long running problem with remote access to network resources. This is the other half of why I needed that utility to change the mapping for a drive letter depending on which network the user was connected to.
Due to the speed (or lack thereof) i had put off even trying until recently. The service we use for CLOUD storage of these fies has to run a client program to function. This "client" effectively hides "what is really happening" so the user thinks their files have magically popped up in their cloud storage in seconds. Naturally they keep loading more till done. All that really happens is that the title of the file (or maybe not even that) is loaded long before all the data is transmitted so it LOOKS like it is there, but only to the person who just uploaded it.
No one wants to see the REAL speed of a 10MB upload to a cloud drive over a wifi connection running off a cellular router that probably is not even connected to 3G.
Network speed is always going to be a problem but i would rather the Users SAW their file was "in transit" and not THINK that they can shut down their system and forget it. The others in their group who are patiently waiting for those files to show up in the shared folder eventually complain. To me of course. The UPloader swears they saw the file "Go uP" so it must be IT 's fault?
Windows 8.1 plainly offers the option of creating a "network Place" just like Windows 7. Then adds the extra magic of offering to "View Ftp Site in File Explorer" which THEN offers you "Easy Access" to "Map as Drive".
Wow. If only it worked.
Everything works as it should including the user and password verification (which you have to do twice though it doesn't tell you that). This would not be quite so bad if it were not for the fact that if you BUY a 3rd party program, ( Like WebDrive )you CAN do it just as easy (or easier) than above. But only with their help.
No one I have asked seems to know why. Webdrive sure isn't going to tell me but why would MS put in something that useful and then NOT make it work? Can't even map a drive letter to MS One Drive as far as I know.
Anyway, if anyone has a clue as to what the issue is, it would be appreciated. So many people have posted that the thing works when all they are getting is the same old "Network Place" which will not work as a reference point in a database program. It MUST be on a specific drive letter referenced path.
Due to the speed (or lack thereof) i had put off even trying until recently. The service we use for CLOUD storage of these fies has to run a client program to function. This "client" effectively hides "what is really happening" so the user thinks their files have magically popped up in their cloud storage in seconds. Naturally they keep loading more till done. All that really happens is that the title of the file (or maybe not even that) is loaded long before all the data is transmitted so it LOOKS like it is there, but only to the person who just uploaded it.
No one wants to see the REAL speed of a 10MB upload to a cloud drive over a wifi connection running off a cellular router that probably is not even connected to 3G.
Network speed is always going to be a problem but i would rather the Users SAW their file was "in transit" and not THINK that they can shut down their system and forget it. The others in their group who are patiently waiting for those files to show up in the shared folder eventually complain. To me of course. The UPloader swears they saw the file "Go uP" so it must be IT 's fault?
Windows 8.1 plainly offers the option of creating a "network Place" just like Windows 7. Then adds the extra magic of offering to "View Ftp Site in File Explorer" which THEN offers you "Easy Access" to "Map as Drive".
Wow. If only it worked.
Everything works as it should including the user and password verification (which you have to do twice though it doesn't tell you that). This would not be quite so bad if it were not for the fact that if you BUY a 3rd party program, ( Like WebDrive )you CAN do it just as easy (or easier) than above. But only with their help.
No one I have asked seems to know why. Webdrive sure isn't going to tell me but why would MS put in something that useful and then NOT make it work? Can't even map a drive letter to MS One Drive as far as I know.

Anyway, if anyone has a clue as to what the issue is, it would be appreciated. So many people have posted that the thing works when all they are getting is the same old "Network Place" which will not work as a reference point in a database program. It MUST be on a specific drive letter referenced path.











