| Prev | Advanced Operations Guide | Next |
Win32 Client Configuration Parameters
The client configuration options are available in all the different installation setups. These options must be configured separately for each workstation, which includes servers acting as workstations.
Access
Gateway Durability
This option specifies whether the MicroKernel Router should store in the registry a list of computers that do not have Pervasive.SQL running on them. This decreases the time it takes to find a gateway engine. You must set this option to Off when new engines are added to the workgroup.
Number of Load Retries
This setting specifies the number of times the MicroKernel Router attempts to connect to the target engine.
Target Engine
This setting applies only to the client running on a Windows NT/2000 server where a database engine is installed. This setting is ignored on Windows 9X/ME. If you are running on Windows9X/ME, setting this value to "Server" is not permitted.
If you have both a Workgroup engine and a Server engine installed on the Windows server, you can use this setting to shorten the initial connection time for the engine that you use the most. If you use the Server engine most often, you can set it to Try Server, then Workgroup so that the client always tries to connect to the local Server engine first.
If you have only a Workgroup engine installed, setting this parameter to Workgroup avoids the wait that occurs when the client tries to open a named pipe to a non-existent local Server engine.
If the client occasionally access both a remote Server engine as well as the local Server engine, you can use this setting to determine which engine the client connects to. In this scenario, the remote Server engine is referred to as the Workgroup.
If the setting Use Local MicroKernel Engine is turned Off, then this setting is ignored.
Use IDS
This setting specifies that the MicroKernel Router allows access to a Pervasive.SQL I*net Data server running on a remote server. Make sure this setting is set to On before using any of the IDS configuration options.
Use Local MicroKernel Engine
This setting determines whether a local application tries to connect to a local engine. If set to Off, no attempt is made to connect to a local engine.
Use Remote MicroKernel Engine
This setting specifies whether the MicroKernel Router allows access to a Server or Workgroup engine running on a remote server. If this value is set to On, and Use Local MicroKernel Engine is set to On, the remote server is tried first.
Prior to Pervasive.SQL 2000i (Service Pack 3), this setting was named "Requester."
Note
We recommend you keep Use Remote MicroKernel Engine set to On for a Microsoft's File and Print Services for NetWare (FPNW) server running Pervasive.SQL. You may receive a Status Code 94, "The application encounter a permission error," if you change this setting to Off when you are running the Btrieve Interface locally on the FPNW server and using a local FPNW drive mapping or local FPNW UNC path.
Cache Engine Debugging
The settings available under Cache Engine Debugging perform the same functions for the client cache as similar settings under Server | Debugging perform for the main database engine. For more information about each setting, see the related server setting.
Number of Bytes from Data Buffer
Number of Bytes from Key Buffer
Communication Protocols
Enable Auto Reconnect
This setting specifies whether you want the client to attempt to auto-reconnect during a network outage. A setting of On means Auto Reconnect is enabled.
Auto Reconnect is not in effect unless this setting is also enabled in the server configuration.
Supported Protocols
This setting specifies the protocols that are used by the Communications Requester. If more than one protocol is specified, the Communications Requester attempts to connect using all available protocols. When the first protocol succeeds, that protocol is used for the remainder of the session. The default value varies depending upon the platform; the available options are:
Table 5-6 Supported Protocols
You must have at least one specific protocol that is enabled at both the client and the server, or else they cannot communicate.
Connection Timeout
The value of this setting specifies how long the client waits while searching for or connecting to a remote database engine. If this value is set too low, the client may return spurious "server not found" errors, because it is timing out before it has a chance to complete the connection. If the value is set too high, when the client attempts to connect to a server that is not reachable, you may encounter lengthy delays before receiving an error. Generally speaking, a value between 15 and 30 seconds is adequate for most networks. If you receive many "server not found" errors, try a higher setting.
This setting was previously named: TCP/IP Timeout for Communication Requester.
Performance Tuning
Compress IDS Data
This setting determines if the MicroKernel Router uses compression with the IDS server. Using compression may allow the data to be transmitted in fewer TCP/IP packets and may improve performance.
Use Cache Engine
This setting specifies whether the client cache should be used. If this setting is Off, then the client caches single records in a relatively small fixed-size cache on the client workstation. If this setting is On, then the client uses the client cache engine, if it is loaded in memory. If the client cache engine is not loaded, this setting has no effect.
The client cache is similar in many ways to the Workgroup engine. By default, it auto-loads into memory when an application first accesses the database, and it unloads a few minutes after that application is stopped. After the client cache engine starts, a tray icon appears, allowing you to control the client cache from the Windows task bar.
Some users may wish to keep the client cache in memory at all times, to avoid the performance cost of re-populating the cache with each usage session. If you want to keep the client cache loaded, simply run it from the Pervasive program group menu before you start any applications that use the database engine.
To run the client cache, choose Start4Programs4Pervasive.SQL V84Engines4Cache Engine.
To stop the client cache, right-click on the client cache tray icon and choose Stop Engines and Exit.
Pervasive.SQL keeps the client cache fully synchronized with the database engine cache and other client cache locations. This behavior is entirely transparent, meaning that you should never need to worry about what records are or are not in any given client cache.
The following operations are not stored in the client cache:
- everything inside a transaction
- operations with a lock bias
- write operations such as insert, update, delete
- opens and close operations
Security
IDS Password
This is the password used by the MicroKernel Router to log into a Pervasive.SQL I*net Data Server running on a remote server. There is no default value and a password must be set by the system administrator on the I*net Data Server and the Use IDS configuration option must be set to On before using this option.
IDS Username
This is the name used by the MicroKernel Router to log into a Pervasive.SQL I*net Data Server running on a remote server. There is no default value and a user name must be set by the system administrator on the I*net Data Server and the Use IDS configuration option must be set to On before using this option.
Runtime Server Support
No
user_name:passwordThis setting controls runtime server support. If enabled with the value Yes, the current user name and password for the drive on which you are presently running are used. To enable RTSS with a different username, enter "user_name:password".
SUPERVISOR and ADMIN are not valid user names, even if supplied with the correct password. If the requester cannot find a login user name other than SUPERVISOR or ADMIN, it does not attempt to login.
Application Characteristics
Embedded Spaces
This option instructs the Btrieve Interface to allow embedded spaces in filenames for Btrieve operations.
Splash Screen
This setting controls whether or not the Btrieve Interface splash screen displays. The splash screen displays the first time a Btrieve requester is loaded.
The 32-bit Configuration utility enables/disables the splash screen for 32-bit applications and 16-bit applications when thunking is set to On. For 16-bit applications, if thunking is set to Off, use the Client-16-bit Application characteristics options to disable the splash screen.
Configuration Mapping
The following table is a mapping of all the available Client configuration options and their settings.
| Prev Server Configuration Parameters |
Contents Up Check for Revisions | Next Win16 Client Configuration Parameters |