Hope this info helps...
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
*** Pervasive.SQL Service & Support Classes ***
January 26-28, 2000; March 8-10, 2000
See our web site for details!
> 1) Do you think that if we disable the Btrieve cache, this problem will go away
> or be minimized?
Disabling the Btrieve cache will not help, since the phantom corruption problems are
with NetWare's cache instead. Your Btrieve cache should be rather large to support
many users adequately -- expect 16MB as a minimum for 20+ users, and lean towards
32MB or 64MB if you can. This will improve performance -- provided Netware has lots
of free memory.
Quote:> 2) Can I downgrade to v6.10c on a NW5 server - or do I need an NDS aware version
> of Btrieve?
6.10f is really only 6.10c with 4 bug fixes. It is NOT NDS-aware in the slightest.
Quote:> 3) I have acquired PSQL.2000 - will this solve this problem, and if so, how
> hairy an upgrade is it?
Pervasive.SQL 2000 will have NDS-aware components, addressing #2 above. If the
ReadFile() api is your problem, then you should be able to squash this problem with
the File IO Mutex option in PSQL2000 Service Pack 1. Upgrading is fairly easy -- if
you have TCP/IP already running. If not, get it running first. If you can't,
install will be chock full o' workarounds. Remember to save a backup of your SYSTEM
directory so that you can go back if needed.
Quote:> We are running an old DOS based Btrieve app developed in house (in Magic PC
> v3.5). We are moving to Magic v8.3 - but we will have to spend some time in
> v5.7. Due to the DOS based status - I thought the error 2's were occurring
> because user's were not closing down the app correctly from the Windows
> workstation - leaving the customer database in an unknown state. The next time
> the error 2 pops up - I'm going to try the rename/copy, the BSTOP/BSTART and the
> Down server method.
NetWare 5.x doesn't suffer from the TurboFAT cache problem like NW4.x does, but
restarting the server should address ReadFile(). Whenever you have a server engine,
there is nothing a workstation can do to corrupt data files at the Btrieve level.
(Of course, bad application-level data is always possible.)