Hello!

Is there anyone who has experienced a problem using Btrieve V5.10 on an
NT Workstation v4.0 connected to a Novell Network 4.1. When loading
Novll's Btrieve "driver" WBTRCALL.DLL I get a GPF which is done at
application startup of my 16-bit VB application.

I got another computer but with the OS Win3.X connected to the same
network running my application without any problems.

/Mike

Hello Michael

I spent a couple of years supporting a database app that used BTRIEVE and
there was no greater hell than dealing with WBTRCALL.DLL.  The first thing
you need to be aware of is that there are no less than FOUR versions of
this DLL and  they are not at all compatible with each other.

I used BTRIEVE 6.0 on Novell 3.12.  I would first suggest you get off 5.1
and up to 6 if you can

OK, let's talk about the DLLs.  As I said, there are four of them.  The one
you are interested in is 38K in size.  What's special about this DLL is
that  it is designed to load as a driver directly accesible from Windows.
I used it for both 3.1 and 95, will presume it works with NT workstation as
well.  Anyway, the main point is that it does not to require the  DOS level
BREQUEST driver to be loaded.  (Some of the other WBTRCALL versions DO.)
This is important because pre-loading DOS drivers in the 32 bit OS
environment is... difficult.  This particular version also has a supporting
stack of DLLs which you need to make sure you have.  There is a document
from Pervasive that talks about the DLL stack and what versions you need.
Sorry I don't have better details on how to get it.  Will follow up if I
can.

OK, so now you have the right DLL (size=38K) and stack installed on the
workstation.

Next, and this is the tedious part, make sure there are NO OTHER versions
of WBTRCALL ANYWHERE.  And I mean anywhere.  I have been on sight and found
a confliciting version fo WBTRCALL buried under a non-path'd directory on
the Novell server and it screwed everything up.  I got rid of it and things
lit right up.  Kill 'em all.

Last point:  Make sure the workstation is connecting with the NETWARE
client, not to an NT server that then connects to the Netware server.  If
you can get it to work with the MS client, great.  If not, try it with the
Netware client.

It's been a while since I've worked with all this stuff and there's some
good docs on the DLL stacks available from Pervasive.  

Hope this helps.  Good luck.