When you export data to the Microsoft Excel file format, null values are replaced with the data that should be in the next column in the resulting spreadsheet.
This behavior occurs when all of the following conditions are true:
- The first two columns are numeric and contain integer data.
- The third column allows null values.
- The fourth column is the same numeric data type as the first two.
- At least one record contains the exact same values in the first two columns. All subsequent records meeting the criteria in the first three items demonstrate the problem.
- You use the Export command or the TransferSpreadsheet method to export data.
- You are using the Excel ISAM driver, Msexcl40.dll, version 4.0.4331.3.
Use one of the following methods to resolve this problem:
- This problem has been fixed in the latest edition of the Jet Service Pack.
For additional information about how to obtain the latest version of the Jet 4.0 database engine, click the following article number to view the article in the Microsoft Knowledge Base:
How To: Obtain the Latest Service Pack for the Microsoft Jet 4.0 Database Engine
- Set the Export as Formatted option to True. To do so, click to select the Save formatted check box in the Export Table '<name>' To dialog box.
- Use a query that converts the nulls to 0 or zero-length strings rather than exporting the values directly from the table. For example, if the field Text1 contains null values, rather than Text1, your query column would be MyText: Nz(Text1, " ").
- Use the OutputTo action rather than the Export command on the File menu or the TransferSpreadsheet method.
- Change the table design so that the column containing null values allows zero-length strings or uses a zero-length string or 0 as the default value (or both). Use an update query to replace all null values with the appropriate value.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Jet 4.0 SP6.
Article ID: 294410 - Last Review: January 31, 2007 - Revision: 6.5
- Microsoft Office Access 2003
- Microsoft Access 2002 Standard Edition
|kbhotfixserver kbqfe kbarttypedocerr kbbug KB294410|