I'm working on a custom InstallShield Pro 7 install for P.SQL 8.5 client. I
have it working for the most part I think. Getting the right DLLs, registry
entries and registering DLLs. But I'm wondering about getting the client
cache engine to work. I have the Use Cache Engine setting set to YES, but I
don't see the Client Cache Engine configuration settings in PCC that are
cited in the documentation. Can anyone give me some input for getting the
client cache engine to work? Shouldn't I see the icon for it in the system
tray (as well as W3DBSMGR.EXE in memory) when it is operating?

Thanks!

When you set up the client components -- did you set "Use Local Microkernel
Engine" to OFF? If you do this, the options for the cache engine configuration
in the PCC go away.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Pervasive.SQL Service & Support Classes ***
Chicago: March, 2004: See our web site for details!


nobody wrote:

Thanks for the info. So you're saying that in order to use the client
cache, Use Local Microkernel Engine has to be turned on?

Thank,
Bill
"Bill Bach" <bbach (AT) cncdsl (DOT) com> wrote

Honestly, I've not played with it that much. It may just be that the settings
are only available when Local Engine is enabled. I'll have to run some tests...

BB

nobody wrote:

That is correct.
The client cache executable is the same as the workgroup executable.
It is w3dbsmgr.exe.

If you turn off the local microkernel engine it does not get loaded
for workgroup or cache.

The DLL that the executable loads is different.
w3cache.dll
w3mkde.dll

Leonard

On Sun, 08 Feb 2004 22:19:14 GMT, "nobody" <nobody (AT) notproviding (DOT) com>
wrote:

But I cannot determine what it is that makes the system tray icon look
different when the client cach engine is operating. The message box text
one sees when double clicking on the system tray icon is also different for
the client cache engine. I've tried setting local to yes, use cache engine
to yes and even target engine to 2 but I cannot get the client cache icon,
etc.

"Leonard" <lharvey (AT) austin (DOT) rr.com> wrote

I do not know for sure but I believe that the w3dbsmgr changes the
icon on the system tray based on which DLL it can find to load.
w3mkde.dll is loaded first if it is present and is the workgroup
engine. It has client cache functionality also.
If w3mkde is not present it will try to load w3cache.
From what I understand w3cache is more or less the same as the
workgroup except it does not have any file IO so it can not open a
data file on its own.

Only the transactional (Btrieve) API calls go through the client cache
engine. ODBC does not. DTI calls do not go through it either.

If I remember correctly it should still be used when "local" = "no".
I am not sure the PCC can connect to it though.
Setting the "target engine" = "server only" will keep it from being
used. I am not sure what target engine = 2 translates to off the top
of my head, but if it is server only the local engine (workgroup and
cache) are completely skipped.
And of course "use client cache" has to be set to yes.

Going way back the application itself can use a bias on the open to
force using a local engine or a remote engine. I believe if the
application were to pass the "use remote" bias the client cache would
not be used the same as setting target engine to "server only".

Leonard

On Thu, 12 Feb 2004 13:03:03 GMT, "nobody" <nobody (AT) notproviding (DOT) com>
wrote: