PRB: MDAC 2.1 dBase Driver Can No Longer Update DBF Files

ID: Q238431

The information in this article applies to:

Microsoft Data Access Components versions 2.1, 2.1 (GA), 2.1 SP1, 2.1 SP2

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

The latest version of the Microsoft dBase Driver which ships with MDAC 2.1 requires the Borland Database Engine (BDE).

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 additional information about how to contact Merant, Borland.Com, or Inprise Inc., please see the following articles in the Microsoft Knowledge Base:

Q65416 Hardware and Software Third-Party Vendor Contact List, A-K

Q60781 Hardware and Software Third-Party Vendor Contact List, L-P

Q60782 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, please see the following article(s) in the Microsoft Knowledge Base:

Q230126 ACC2000: Using Paradox Data with Access 2000 and Jet

Q230125 ACC2000: Using dBASE Data with Access 2000 and Jet

Additional query words:

Keywords : kbMDAC kbODBC odbcDbase kbDSupport kbMDAC210 kbMDAC210SP2
Version : WINDOWS:2.1,2.1 (GA),2.1 SP1,2.1 SP2
Platform : WINDOWS
Issue type : kbprb