The Connect tab provides options for configuring the connection between a client application (such as SQLWizard or a program that you have developed) and the XDB Server you will be accessing.
| Locations | Specify the name of the default location you want to access when a connection is made (click the BROWSE button if you want to select from a list of locations). You will be able to override this selection at run time if the Connect dialog box is displayed (the AUTOCONNECT option is off and/or CLIENT SECURITY, on the Security tab, is on). | |
| AuthID | Specify the AuthID (user name) you want to appear as the default in the Connect dialog box. You will be able to override this
at run time if the Connect dialog box is displayed when you start SQLWizard (i.e., the AUTOCONNECT option is off and/or CLIENT
SECURITY, on the Security tab, is on).
If security is off, the AuthID entered in Options will automatically become your current SQLID and will be used as the AuthID portion of any database objects you create. |
|
| AutoConnect | If AUTOCONNECT is on and CLIENT SECURITY, on the Security tab, is off, the Connect dialog box is suppressed. In this case, you connect to the default Server, Location and AuthID that you specified in Options. | |
| AutoLogoff | Check this to have the user automatically logged off from the system when you exit the Options Utility if you have made any changes to your connection specifications. | |
| Communication Protocol | Specify which protocol you want to use to communicate with the XDB Server specified in Server Name. Options are: | |
| Local [or Windows(LOCAL)] | (Windows 3.x only) Communicates with a local XDB Server. If you have an XDB Server on the same machine as your client application, you can use this server to communicate with it using the proprietary internal protocol instead of using the network. | |
| Win32Local | (Win32 only) Communicates with a local XDB Server. If you have an XDB Server on the same machine as your client application, you can use this server to communicate with it using the proprietary internal protocol instead of using the network. | |
| NetBIOS | Communicates across the network to a remote, multiuser XDB Server using the NetBIOS protocol. | |
| Names Pipes | Communicates across the network to a remote, multiuser XDB Server using the Named Pipes protocol. (Also may be used to access a local XDB Server that supports local Named Pipes.) | |
| TCP/IP | Communicates across the network to an XDB Server or XDB Link using the TCP/IP protocol.
If you choose the TCP/IP protocol, enter the server's IP address in the IP Address text box, and the port number on which the server will receive connection requests in the TCP Port text box. The same port number must be specified on the XDB Server and all clients of the XDB Server. Check with your system administrator if you do not know this information. |
|
| IPX/SPX | Communicates across the network to an XDB Server or XDB Link using the IPX/SPX protocol.
Note:
You may need to add information to your xdb.ini file to successfully use some of these protocols. See the PROTOCOL= and PROTOCOLMAP= parameters in the [CONNECTION DEFAULTS] section of the xdb.ini file for more information. Check with your network administrator and your XDB Server Administrator to determine which protocols are supported on your network and on your XDB Server. |
|
| Client Node Name | This is the name by which your machine is known to the XDB Server. The name should be unique among all machines that are trying to access any XDB Server or XDB Link on your network. |