You'll need to find out which status code is coming back. If Maximizer
doesn't give you back a numeric status code, then you'll need to force
one. Assuming that you have Pervasive.SQL 2000i, you'll have to enable
the MKDE Tracing feature on either the server (if you are using the
server engine) or the client (if you are using the Workgroup Engine).

Also, check to see if any old Btrieve 6.x engines are still hanging
around -- look for WBTR32.EXE or W32MKDE.EXE files left on your
workstation from some other application.
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: June, 2004: See our web site for details!


Ed and Donna wrote:

IMSMW Maximizer 5.5 comes with Btrieve 6.15. Ed doesn't say anything
about running Pervasive, so I'd expect hime to either use the 6.15
workstation engine or even Novells 6.10 engine. In fact if he upgraded
this version of Maximizer from one that's even more ancient he may
still have tables in pre-version 6 format.

So Ed, get us more info:
- version of Novell
- version of BTRIEVE.NLM
- version of Btrieve/Pervasive you're using with Maximizer
and type: workstation or client-server

if running client-server:
- what client do you use to access Novell (Microsoft won't do)
- network protocol

If you know what file Maximizer has troubles with (MXZU.MAX?) and you
have access to a utility called BUTIL (runs in DOSbox) what does it
say when you run BUTIL -STAT <file>

Gordon

On 11 May 2004 22:07:54 EDT, Bill Bach <bbach (AT) cncdsl (DOT) com> wrote:


Gordon Bos
Q-RY Solutions
+31-(0)15-2564035

http://www.q-ry.nl/

NetWare 5.1 came with a 2 user Pervasive.SQL 2000 SP1 out of the box.

To double check either do a "load config" and examine the
sys:system\config.txt file that is produced or type "modules" at the
command line on the server.

The modules of particular interest are:
btrieve.nlm
nwmkde.nlm
bspxcom.nlm
btcpcom.nlm

To double check Pervasive server licensing type "nwucutil -g11" on the
server console.

Leonard

On Wed, 12 May 2004 22:16:01 GMT, Ed and Donna <Ed_Donna@!!!!.org>
wrote:

Like Leonard said, NetWare 5.1 has a default install of Pervasive.SQL
2000. I have seen many situations though where the Pervasive 2000 was
substituted by the old Btrieve 6.10. When you say BTRIEVE.NLM is a
really old file (1987 or earlier?) I'd say that might be the case with
your server and that would not comply with you claiming to have
Pervasive.SQL 2000.

To find out what version you're running, go to the NetWare console and
type " MODULES B* ". This will output information about the loaded
modules that start with the letter B, including BTRIEVE.NLM and
BSPXCOM.NLM and/or BTCPCOM.NLM.

Check your Maximizer data directory and delete every file with
extension .LCK. If the files cannot be deleted because they're in use
or if they reappear when you start Maximizer on one of the Windows 98
stations, you're using Btrieve 6.15 workstation engine.

Check versions of WBTRCALL.DLL and WBTRV32.DLL on your workstations.
If the NetWare modules are version 7.5 or above and you have
sufficient licenses installed, these DLLs should also be version 7.5
or above (filesizes approx 30k and 40k accordingly).

Gordon

On Wed, 12 May 2004 22:16:01 GMT, Ed and Donna <Ed_Donna@!!!!.org>
wrote:



Gordon Bos
Q-RY Solutions
+31-(0)15-2564035

http://www.q-ry.nl/