Network Path Formats Supported by Pervasive Requesters
When using your Requester, you connect to the Pervasive server engine to access data files. This section shows the variations on network file syntax you can use to access files on your network using Btrieve or DTI applications.
Pervasive PSQL supports the Universal Naming Convention (UNC) and Drive path formats (explicit and current) across the majority of operating environments.
For more information on the path formats, see the sections that follow:
•
Universal Naming Convention (UNC) Path Formats
•
Drive-based Formats
•
Linux Path Formats
If you are an application developer, also note that the certain access methods, such as the Btrieve API, support URI connection strings. For details about URI strings, see
Database URIs
in
Pervasive PSQL Programmer's Guide
. In
Btrieve API Guide
, see
Create (14)
,
Open (0)
, and
Login/Logout (78)
.
Universal Naming Convention (UNC) Path Formats
The following UNC path formats are supported on all clients to all servers:
\\ServerName or IP address\share\path\file
\\ServerName or IP address\share:[\]path\file
UNC syntax is resolved correctly regardless of the actual type of network operating system (NOS) running on the target server. If you use an IP address, it must be a dotted IPv4 address or one of the two formats supported for IPv6. See
IPv6 Addresses
.
Note:
In all instances above, backslashes (\) can be interchanged with forward slashes (/) except for the double backslash (\\). The syntax [\] indicates that the backslash is optional.
Drive-based Formats
The following drive representations are supported on all clients to all servers:
drive:file
drive:[\]path\file
file
[\]path\file
..\file
Linux Path Formats
Incoming paths on a Linux server using Samba will be processed as follows in order of relative priority:
Share names
\\
<server>
\
<sharename>
\
<path>
The smb.conf file must be configured to accept <
sharename
>, otherwise it will default to the following:
Absolute paths
\\
<server>
\
<absolute_path>
If the smb.conf file is not configured properly or not found on the target server, the absolute path is used.
For more information on the Linux version of Pervasive PSQL v11 SP3, see
Using Pervasive PSQL on Linux
.
Note: In all instances above, backslashes (\) can be interchanged with forward slashes (/) except for the double backslash (\\). The syntax [\] indicates that the backslash is optional.