I may have posted something about this before...
I'm dealing with a shared drive network where not everyone using it has the same locations mapped as the same drives.
For example, I might have a network folder mapped as drive G:\ whereas my coworker may have the same folder mapped as drive K:
But if we both enter the network address in Windows File Explorer, for example, \\100.10.10.111\public\ we're both seeing the same folder.
Now here's my issue: VisualNeo action commands like FileCopy, FileErase, FileRename, etc. will allow me to use either the mapped drive location or the network address but FM/FTP will not. I can only use a mapped drive for a file location. Obviously FM/FTP has many more extensive file managing actions that native VisualNeo doesn't. This seems to be a significant limitation, at least to me. I've even tried using remote connection with no success.
Is there a reason FM/FTP doesn't work this way? Am I missing something? Or is there a way to fix this?
Thanks.
I may have posted something about this before...
I'm dealing with a shared drive network where not everyone using it has the same locations mapped as the same drives.
For example, I might have a network folder mapped as drive G:\ whereas my coworker may have the same folder mapped as drive K:
But if we both enter the network address in Windows File Explorer, for example, \\100.10.10.111\public\ we're both seeing the same folder.
Now here's my issue: VisualNeo action commands like FileCopy, FileErase, FileRename, etc. will allow me to use either the mapped drive location or the network address but FM/FTP will not. I can only use a mapped drive for a file location. Obviously FM/FTP has many more extensive file managing actions that native VisualNeo doesn't. This seems to be a significant limitation, at least to me. I've even tried using remote connection with no success.
Is there a reason FM/FTP doesn't work this way? Am I missing something? Or is there a way to fix this?
Thanks.