PRB: dBase Driver Cannot Update DBF Files in MDAC 2.1 and Later Versions

This article was previously published under Q238431
This article has been archived. It is offered "as is" and will no longer be updated.
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), Borland.Com (http://www.borland.com), and Inprise Inc. (http://www.Inprise.com). For more information about hardware and software vendor contact information, visit the following Microsoft Web site: 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 theMicrosoft Knowledge Base:
230126 ACC2000: Using Paradox Data with Access 2000 and Jet
230125 ACC2000: Using dBASE Data with Access 2000 and Jet
Properties

Article ID: 238431 - Last Review: 02/28/2014 00:27:59 - Revision: 5.2

Microsoft Data Access Components 2.1, Microsoft Data Access Components 2.1 Service Pack 2, Microsoft Data Access Components 2.1 Service Pack 1, Microsoft Data Access Components 2.1 Service Pack 2, Microsoft Data Access Components 2.5

  • kbnosurvey kbarchive kbprb KB238431
Feedback