Microsoft KB Archive/269663

= ACC97: FoxPro File Imported or Linked by Using ISAM Driver Shows Data Where Null Should Be =

Article ID: 269663

Article Last Modified on 1/27/2007

-

APPLIES TO


 * Microsoft Access 97 Standard Edition

-



This article was previously published under Q269663



Moderate: Requires basic macro, coding, and interoperability skills.



SYMPTOMS
When you use the FoxPro ISAM driver that is included with Microsoft Access 97 to import or link a Microsoft Visual FoxPro 3.0 file that has fields that contain nulls, you notice that those fields now contain data.



CAUSE
The fields originally contained data, and then later, this data was replaced by nulls in Microsoft FoxPro. The FoxPro ISAM driver does not recognize this, and instead shows the original data of those fields.



RESOLUTION
To display the information correctly, link or import the file by using the Visual FoxPro ODBC driver rather than the FoxPro ISAM driver.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
This problem occurs only when a null is inserted into a field that originally contained data. If a field has never contained data, that field correctly shows the null in Access 97.

Steps to Reproduce the Behavior

 * 1) Create a file in Visual FoxPro 3.0 that has two fields: a Text field and a Numeric field. Set the Numeric field to allow nulls.
 * 2) Enter a few sample records in FoxPro.
 * 3) Import the table into Access by using the FoxPro ISAM driver. Note that the information appears correctly.
 * 4) Open the file in FoxPro again, and then insert nulls into the Numeric field in one or more records.
 * 5) Import the table again into Access 97. Note that the original data still appears.

Additional query words: pra

Keywords: kbbug kbnofix KB269663

-

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

© Microsoft Corporation. All rights reserved.