Par2: Using UNC paths
1999-06-02 -- Ron Phillips
I specify my data file names as variables and use an INI file with UNC paths
to the data files, just as you describe. Works well, so far.
> also with Dictionary files using a variable
> pathname that could contain a UNC path (e.g. File pathname is
!Glo:FileName
> contains something like \\Server\Program Files\MyApp\CUSTOMER.TPS instead
> of the more traditional network convention of F:\Program
> Files\MyApp\CUSTOMER.TPS).
TJ adds:
UNC paths require a connection to the server they reference. When a
program uses a UNC path for the first time, it has to connect. It
usually tries to use your user id and password to establish the
connection. It may fail if the user logged into the machine attempting
the connection has no rights to access the UNC path.
When you map a drive, you manually specify the user and password. In
NT you can even specify a domain name and a user other than the one
currently using the machine.
After the drive has been successfuly mapped, there will not be any
"rights" issues. The client machine has established a permanent
connection to the server by virtue of the drive mapping.
UNC paths work fine in CW5. I am using them. But keep in mind that
client/server connections are hard to manage (and debug) when UNC
paths are used.
Printed November 21, 2024, 7:34 am
This article has been viewed/printed 35202 times.