Not specifically relevent, but something that I needed to keep in mind...
In a Windows-centric network environment, you can utilize UNC drive mappings if running across the network. (you should use UNC's whenever possible, users can change drive letter mappings at will!)
I.E. If desiring to write to a network resource, try to avoid "drive letter" mappings like
x:\somedirecotryonaserver\subdir\filename
<code>
<p>
and use:
</p>
<code>
\\server\sharename\subdir\filename
In perl, be sure to escape all the slashes, and if your admins use the dollar sign$ for shares, be sure to escape that too!
ala
open FH, ">\\\\server\\sharename\$\\subdir\\filename" or die "cannot o
+pen file: $!";
|