Very Computer

There are three settings which work together:
1) Requester: If this is enabled, the system will attempt to contact a
server engine when remote data files are being accessed.  This plays no
part when the data files are on the local hard drive.  If a remote
server engine is not found to handle the requested file, the system
continues with the other options normally.
2) Local: If this setting is enabled, the system will attempt to load a
Win32 workstation engine (WSE).  On Win9x, it will look for either
W3DBSMGR.EXE first.  If not found, it will search for W32MKDE.EXE (the
6.15 engine) next.  If the engine is found and the files cannot be
opened with the Requester, then the local engine is passed the files to
access.   On a Windows NT Server running the Client/Server Engine (CSE),
this setting also allows the system to direct requests to the CSE
(NTDBSMGR).
3) Target Engine: On Windows NT platforms, when *BOTH* a CSE and WSE are
found on the local machine, this setting controls who gets requests
coming from processes running on the server.  In other words, if you run
an application on the server itself, this setting will dictate that
requests (when Local=Yes) should be sent to the WSE (Workstation Only)
or to the CSE (Server Only).  If only one engine is found, then this
setting has no bearing on the final outcome -- all requests will go to
that one engine.  Note that since the CSE cannot run on Windows 9x, this
setting is meaningless on these platforms.

Since you indicated that you ran the client setup, I presume that you
have no server engine on the machines you are installing to.  In that
case, you have no need to change the Target Engine setting.  (I would
recommend changing Local to No, though, to improve startup time.  While
I don't think you can change the defaults (since they are set by the
requesters, bot by the setup utility, it would be very easy to configure
one machine, export its registry, and then just import the registry
settings into each other machine as you install them.  (Three extra
mouse clicks.)
 Goldstar Software Inc.
 Building on Btrieve(R) for the Future(SM)
 Bill Bach

 www.goldstarsoftware.com
 *** Btrieve/Pervasive.SQL Development Classes ***
 Chicago: May 14-18, 2001 - See our web site for details!
 *** Pervasive.SQL Service & Support Classes ***
 Chicago: June 19-22, 2001 - See our web site for details!