Microsoft KB Archive/100514

= UPD: New XBASE Driver Available That Fixes Several Problems =

PSS ID Number: 100514

Article Last Modified on 6/14/2004

-

The information in this article applies to:


 * Microsoft Visual Basic Standard Edition for Windows 2.0
 * Microsoft Visual Basic Standard Edition for Windows 3.0
 * Microsoft Visual Basic Professional Edition for Windows 2.0
 * Microsoft Visual Basic Professional Edition for Windows 3.0

-



This article was previously published under Q100514



SUMMARY
A new XBase IISAM driver XBS110.DLL version 1.10.0002 is available. This driver fixes several bugs documented below. It is the same driver that is provided with Microsoft Access version 1.10.



MORE INFORMATION
The following file is available for download from the Microsoft Download Center:

Xbs110.exe

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file. If you have Windows for Workgroups, you can use the following steps to get the version number of your XBase driver:


 * 1) Start File Manager
 * 2) Find the XBS110.DLL file, and select it. This file is usually located in the WINDOWS\SYSTEM directory.
 * 3) From the File menu, choose Properties.

The item marked "Version:" is the XBase version number for XBS110.DLL.

Bugs Fixed by XBS110.DLL Version Number 1.10.0002
PROBLEM ID: 2186

Relates to DBase III

An update is allowed that violates unique index. Using the XB110.DLL driver that shipped with Visual Basic, it is possible to add multiple records that share the same unique index. The new version of the driver does not allow you to update the database with a record that contains the same unique index value as an existing record.

PROBLEM ID: 2390

Relates to FoxPro 2.5

A general protection (GP) fault occurs when updating the record immediately preceding a record locked by another user. The GP fault occurs in XBS110.DLL at 0002:11DA.

PROBLEM ID: 2418

Relates to DBase III

A unique index is corrupted after an update query. The symptom of this problem is that the first 239 items in the table are not found.

PROBLEM ID: 2432

Relates to DBase III, IV and Fox Pro 2.0, 2.5

SeekEQ on NULL returns first non-null record when there are no NULL records in the column.

PROBLEM ID: 2457

Relates to: FoxPro 2.5

Attempting to update a record results in a GP Fault in XBS110.DLL at 0013:144A when the IDX index type is used.

PROBLEM ID: 2487

Relates to FoxPro 2.5

A GP fault in XBS110.DLL occurs at 001A:05F6 when using INSERT INTO on the same table as the FROM clause uses -- that is, when copying records from a table into itself.

PROBLEM ID: 2511

Relates to FoxPro 2.0 and 2.5

A GP fault in XBS110.DLL occurs at 0002:11DA when inserting the 98th record in table that has one index.

Additional query words: update3.00 GPF

Keywords: kbdownload kbenv kbfile KB100514

Technology: kbAudDeveloper kbVB200 kbVB300 kbVB300Search kbVBSearch kbZNotKeyword2 kbZNotKeyword6

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.