>I am having trouble with indexes becoming regulalry corrupted.
> Problem manifests itself as users are running the application and have it lock up with the cursor set to the
> hourglass. Sometimes a windows 95 illegal operation occurs. Specs are below.
> The code at this point is attempting some index related function ie: set key to, seek, set order to, or executing a
> function which implements Rushmore, etc. Problem can be recreated using any of these methods. Problem is with
> ONLY a specific tag within the CDX. Using functions with other tags set doesn't recreate the problem.
> Somehow the index has been corrupted. We delete the tags and rebuild from scratch using a data dictionary
> each time we rebuild. Doing this reindex is the only way to get the users back on line without the lock-ups. It is
> imperative that I identify the cause, since it results in the system being down for excessively long periods of time
> for each reindex.
>
> Application is written in Foxpro 2.6 for windows.
> WorkStations are running Windows 95 with Novell Client 32 versions 2.2 ,3.01, 3.11 .
> Server is Novell Netware version 4.11 with patch 6.
> Network is ethernet.
>
> Currently we are updating all workstation clients to 3.1 with Cache writes set to off and file cache level set to
> zero. This is related to a knowledge based article from Novell.
> Any help or suggestions will be sincerely appreciated.
> Thank you in advance.
>
> Steven Marin

We have had numerous problems with the Novell client and databases (fp2.x, vfp5.0). We opened a ticket with MS and Novell, and researched for several months and came up with these hard to sell solutions...
1. Install Windows NT WS if you must use Client32
2. Install MS Client for Netware
A few shops have fought with us, but the corruption happens with the Novell client and not with the MS Client. You can find numerous articles at Novell and Microsoft's site dealing with the corruption issue.

HTH
Wayne