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 SQL applications.

Pervasive.SQL supports the Universal Naming Convention (UNC) and Drive path formats (explicit and current) across the majority of operating environments, including:

Table 7-1 Supported UNC and Drive Path Formats
Application Types	Environments	Network Client	Novell Login Types
Transactional	Windows (32-bit)	Microsoft	Bindery
Relational	Windows (16-bit)	Novell	NDS
	DOS

For more information on the path formats, see the sections that follow:

Universal Naming Convention (UNC) Path Formats

Drive-based Formats

NetWare Specific Formats

Linux Path Formats

Universal Naming Convention (UNC) Path Formats

The following UNC path formats are supported on all clients to all servers:

\\ServerName\volume\path\file 
\\ServerName\volume:[\]path\file

UNC syntax is resolved correctly regardless of the actual type of network operating system (NOS) that is operating on the target server.

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:

Note
Do not map drive letters to the \\Tree\VolumeObject format found in Network Neighborhood. See NetWare Directory Services (NDS) Formats .

drive:file 
drive:[\]path\file    
file 
[\]path\file 
..\file

NetWare Specific Formats

NetWare path formats on all clients only to NetWare servers:

volume:[\]path\file (ServerName is derived from current 
drive)

NetWare Directory Services (NDS) Formats

Pervasive.SQL provides complete integration with Novell Clients, which has the following benefits to users and network administrators:

Better integration with NDS authentication capabilities when accessing the Pervasive.SQL Server Engine for NetWare.

Ability to resolve server names into network address by querying NDS instead of relying on the NetWare Bindery.

Support for NDS Volume and Directory Map objects in Btrieve file operations.

Note
Pervasive does not support the \\Tree\VolumeObject format found in Network Neighborhood. See NetWare Directory Services (NDS) Formats .

Support for Novell Clients for NetWare

Pervasive.SQL was tested with the following Novell clients:

Novell Client for Windows 2000/2003/XP 4.90

Novell Client for Windows 98/ME 3.40

Each of these clients provide the set of NDS specific APIs needed by the Pervasive.SQL requesters to integrate fully with the NDS environment. All Pervasive.SQL requesters will detect these clients' presence automatically; no additional Pervasive.SQL configuration changes are required. When these clients are available to the Pervasive.SQL requesters, the following operations are supported:

Network login via NDS (bindery context does not need to be set on the target server)

NetWare server address resolution for SPX addresses

Drive letters mapped to NDS Volume Objects through either the Map utility or Network Neighborhood may be used to specify Btrieve file names or SRDE dictionary and data directories

NDS Volume Objects and Directory Map Objects may be used to specify Btrieve file names with Win32, and Win16 applications

The file name and path formats supported by the Pervasive.SQL requesters through the Novell clients are listed in the table below:

Table 7-2 File name and Path formats for Novell Clients for NetWare
Format	Btrieve Apps	Notes	SQL Apps
<drive letter>:[\]path\file		(1)
\\server\volume\path\file
\\server\volume:[\]path\file
server\volume:[\]path\file
volume:[\]path\file		(4)
VolumeObject:[\]path\file		(2) (3)
\\VolumeObject\path\file		(2) (3)
DirectoryMap:[\]path\file		(2) (3)
\\DirectoryMap\path\file		(2) (3)
\\Tree\VolumeObject\path\file
\\Tree\DirectoryMap\path\file

1 <drive letter> can be redirected to a server\volume:, or NDS Volume or Directory Map object.

2 Not supported by the Btrieve DOS requester.

3 See Novell documentation for rules about specifying NDS context when using NDS objects.

4 Requires that the current drive is mapped to the target NetWare server.

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.