PRB: dBase Driver Cannot Update DBF Files in MDAC 2.1 and Later Versions
This article was previously published under Q238431 SYMPTOMS
You may encounter a variety of ODBC error messages when accessing dBase databases which had been successfully accessible with prior versions of the Microsoft dBase Driver.
CAUSE
Versions of MDAC 2.1 and later require the Borland Database Engine (BDE) to update dBase DBF files.
RESOLUTION
There are two resolutions. One is to obtain the BDE: Contact Inprise Inc. or a third-party vendor to obtain the BDE. Obtain licensing and run-time distribution requirements for the BDE from Inprise. Third-party dBASE ODBC driver vendors include Merant (http://www.merant.com (http://www.merant.com)), Borland.Com (http://www.borland.com (http://www.borland.com)), and Inprise Inc. (http://www.Inprise.com (http://www.borland.com)). For additional information about how to contact Merant, Borland.Com, or Inprise Inc., please see the following articles in the Microsoft Knowledge Base: 65416 (http://support.microsoft.com/kb/65416/EN-US/) Hardware and Software Third-Party Vendor Contact List, A-K
60781 (http://support.microsoft.com/kb/60781/EN-US/) Hardware and Software Third-Party Vendor Contact List, L-P
60782 (http://support.microsoft.com/kb/60782/EN-US/) Hardware and Software Third-Party Vendor Contact List
The other option is to use the Microsoft FoxPro VFP Driver that ships with MDAC 2.1 to access the DBF files. To use this driver to access dBase files, select the Free Table Directory option when creating a DSN.
STATUS
This behavior is by design.
REFERENCES
For additional information, see the following article or articles in the
Microsoft Knowledge Base: 230126 (http://support.microsoft.com/kb/230126/EN-US/) ACC2000: Using Paradox Data with Access 2000 and Jet
230125 (http://support.microsoft.com/kb/230125/EN-US/) ACC2000: Using dBASE Data with Access 2000 and Jet
APPLIES TO
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
