|
To Set Up Database Access on a NetWare Server from a Client Workstation
Note
This scenario is the only option for NetWare. You must create both the Client and the Engine DSNs from the client workstation using PCC or ODBC Administrator.
If you have not done so already, please review Prerequisites to Setting up Database Access before proceeding.
The PCC Namespace contains a list of database engines that have been registered.
The PCC Namespace contains a list of database engines that have been registered.
You must register the remote NetWare server with PCC. To do so, right-click on Pervasive.SQL Engines then click Register New Engine.

A dialog box is displayed that allows you to choose the machine name where the Pervasive.SQL server resides.


If the database already appears, then it already has an Engine DSN and you need only set up the client machines with Client DSNs. You are finished with this procedure. Go to Setting Up Client Access for instructions on how to set up the client machines with Client DSNs.
If you do not see the name of the database to which you want to connect, continue with step 6.


In the Directory field, specify the location of the data files.
Note
The Server engine cannot interpret mapped drive paths. You must specify a full path (not a mapped drive) that makes sense on the server. For example, if you have a mapped drive S:\data1\datafiles on your client, referring to the folder SYS:\servers\data1\datafiles on the server, you must enter the server-based directory, \\servname\SYS:\servers\data1\datafiles.
If you wish to use any advanced features, such as specifying that the DDFs and data files are not located in the same directory, that the DDFs and data files are located in multiple directories, or modifying the default DBNAME settings, you must click the Use advanced settings option.
The final wizard step verifies the successful creation of the database.

The database is ready to access. Proceed to setting up client DSNs as explained in Setting Up Client Access .

In the DSN Open Mode field, choose Normal unless you have reviewed the other options as described in Advanced Operations Guide.
In the Database name field, choose the DBNAME of the database for which you wish to create the Engine DSN. If you find the DBNAME you want, click Next and return to step .
If the database you want to access is not listed, click the Create button to create an internal DBNAME for the database. Click Next and continue with the next step.

Leave Integrity enforced checked if you plan to enforce the referential integrity rules defined in the database. Usually it is a good idea to do so.
Click Bound (DDFs created) if you want to prevent any other databases from being associated with these DDFs and data files. Checking this option creates a new set of empty DDFs. Do not click this option if you are setting up access to an existing database.
In the Dictionary location box, type or select the location of the DDFs. As previously cautioned, do not enter or browse a mapped drive path because the Server engine cannot interpret mapped drive paths. You must enter a full path name.
Caution
Browsing for the location only works if you are using the server itself or you are browsing a local directory tree that is identical to the directory tree on the server. Ensure that you enter a full path name.
In the Data file location box, you must accept the default or browse to the location of the data files. As noted previously, browsing for the location only works if you are seated at the server or you are browsing a local directory tree that is identical to the directory tree on the server.
Click OK to close the Create Database Name window. This returns you to the Create Database Wizard.
|
Chapter contents
Prev topic: Setting Up Database Access on Windows
|