Article ID: 123590
Article Last Modified on 7/5/2002
APPLIES TO
- Microsoft Access 2.0 Standard Edition
This article was previously published under Q123590
Moderate: Requires basic macro, coding, and interoperability skills.
SUMMARY
The Microsoft Access version 2.0 Service Pack includes the following new Xbase ISAM:
File Name Size Date
---------------------------------------
XBS200.DLL 296,832 11/20/94 12:00a
MORE INFORMATION
The new Xbase ISAM corrects the following issues using Xbase data with Microsoft Access:
- The new ISAM correctly reads the <filename>.INF file that is created when you attach an Xbase table and provide a unique index. Using the prior ISAM can cause performance problems because indexes are not used correctly.
- The new ISAM translates extended characters in international code pages into Windows ANSI codes correctly for dBASE and Paradox data. In the prior ISAM, extended characters were not always translated correctly. For example, extended character 130 (an accented "e") could be translated as an underscore character ("_").
NOTE: Extended characters in Microsoft FoxPro for Windows data are not translated correctly by the new ISAM driver. For more information about this issue please see the following article in the Microsoft Knowledge Base:
113303 ACC: MS Access Converts Extended Chars in Attached FoxPro DBF
- The new ISAM no longer generates "Invalid disk access" or "Disk I/O" error messages using some multiuser Xbase tables.
- The new ISAM expands the range of valid dates in Xbase tables from 1/1/1753 through 12/31/2078 to 1/1/100 through 12/31/9999.
The new Xbase ISAM is included in the Microsoft Access version 2.0 Service Pack. For information about how to obtain the Service Pack, please see the following article in the Microsoft Knowledge Base:
122927 WX1124: Microsoft Access Version 2.0 Service Pack
Additional query words: jet25 jet 2.5 d-base foxbase iii iv
Keywords: kberrmsg kbinfo kb3rdparty KB123590
