FoxPro Database Corruption with Client32

(Last modified: 23Sep2002)

This document (10016234) is provided subject to the disclaimer at the end of this document.

fact

Formerly TID 2920765

symptom

FoxPro Database Corruption with Client32

 When creating and closing large numbers of files, Client32 corrupts FoxPro databases.

 After creating over 170 files,  the Client doesn't  release the file handle.

cause

The client was designed to only open up to 170 DOS files.  This was the recommendation of the DOS developers kit.  DOS under normal circumstances cannot open more than 170 files, but some Microsoft applications do exceed this limit. The only known database that does this is FoxPro for DOS and Visual Fox Pro.  Any Windows-based application, using Windows APIs should not cause this problem.

Note: Made2Manage is one application that uses FoxPro, and opens more than 170 files.

fix

Turn "Use Extended File Handles" on.

1.  Upgrade to the 3.0 release (and beyond) of the Novell Client for WIN95.
2.  Right click on Network Neighborhood | Properties | Novell NetWare Client | Advanced Settings | Use Extended File Handles = On.  (This setting is off by default)

Notes:
  Some DOS applications such as Fox Pro will require this setting to be set to ON, and that the MAXIMUM FILE LOCKS PER CONNECTION is set at the server for the number of file locks required by the application and client.  This setting will fix the problem caused by this condition only, and may not fix other FoxPro symptoms.  The 3.0 client or above has fixed all known problems with file locking under FoxPro.

document

Document Title: FoxPro Database Corruption with Client32
Document ID: 10016234
Solution ID: 1.0.4402897.2311874
Creation Date: 08Sep1999
Modified Date: 23Sep2002
Novell Product Class:NetWare

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.