Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Date format is not correct when you convert a CSV text file in Excel 2002 by using a VBA macro

Date format is not correct when you convert a CSV text file in Excel 2002 by using a VBA macro

View products that this article applies to.

Symptoms

When you use a Microsoft Visual Basic for Applications (VBA) macro to convert a Comma-Separated Values (CSV) text file into a Microsoft Excel 2002 workbook (*.xls), the format of dates that are converted into your Excel 2002 workbook may not be correct.

For example, in your CSV file, dates may be in the format of:
dd/mm/yyyy
When you run the following macro to convert your CSV text file into Excel, dates may be converted in the following mm/dd/yyyy format:
Sub test()

   Workbooks.OpenText Filename:="C:\Test1.csv", DataType:=xlDelimited, _
      TextQualifier:=xlTextQualifierNone, FieldInfo:=Array(1, 4)
	
End Sub

↑ Back to the top

Resolution

How to obtain the hotfix

This issue is fixed in the Excel 2002 Hotfix Package . For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
829348 Excel 2002 post-Service Pack 3 hotfix package: May 6, 2004

After you install this hotfix, follow the steps that are listed in the "More Information" section of this article to set the VBAAlwaysLoadUS registry key and to activate the hotfix.

↑ Back to the top

Workaround

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. To work around this problem, add the <local:=true> parameter to your VBA macro as in the following example:
Sub test()
	
   Workbooks.OpenText Filename:="C:\Test1.csv", DataType:=xlDelimited, _
      TextQualifier:=xlTextQualifierNone, FieldInfo:=Array(1, 4), Local:=True
	
End Sub

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

↑ Back to the top

More information

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To activate this hotfix, follow these steps:
  1. Quit Excel 2002.
  2. Click Start, and then click Run.
  3. In the Open box, type regedit, and then click OK.
  4. Locate, and then click to select the following registry key:
    HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Excel\Options
  5. After you select the key that is specified in step 4, point to New on the Edit menu, and then click DWORD Value.
  6. Type VBAAlwaysLoadUS, and then press ENTER.
  7. Right-click VBAAlwaysLoadUS, and then click Modify.
  8. In the Value data box, type 00000000, and then click OK.
  9. On the File menu, click Exit to quit Registry Editor.

↑ Back to the top

Keywords: KB835718, kbbug, kbfix, kbofficexppostsp3fix, kbhotfixserver, kbqfe

↑ Back to the top

Article Info
Article ID : 835718
Revision : 5
Created on : 10/9/2011
Published on : 10/9/2011
Exists online : False
Views : 236