Select the product you need help with

XL2000: JPN: VBA Macro Causes Run-Time Error 1004 If AutoComplete Uses IME

Article ID: 279248 - View products that this article applies to.

This article was previously published under Q279248

NOTE: The information in this article applies to the Japanese version%3 of Microsoft Excel 2000.

SYMPTOMS

In Microsoft Excel, when you run a Microsoft Visual Basic for Applications (VBA) macro after you use AutoComplete with the Input Method Editor (IME), you receive an error message that is similar to the following:

Run-time error '1004':

Back to the top | Give Feedback

CAUSE

This problem occurs because Excel incorrectly handles the status of the IME.

Back to the top | Give Feedback

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Office 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

276367

(http://support.microsoft.com/kb/276367/EN-US/ )

OFF2000: How to Obtain the Latest Office 2000 Service Pack

The Japanese version of this fix should have the following file attributes or later. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version     Size       File name       
   ----------------------------------------------------------
   JAN-23-2001  10:50              4,333,568  Excel_Admin.msp 
   JAN-23-2001  10:26              1,716,224  Excel.msp

After the hotfix is installed, the following files will have the listed attributes or later:

   Date         Time   Version     Size       File name
   ----------------------------------------------------
   JAN-18-2001  15:31  9.0.0.4917  7,163,904  Excel.exe

Back to the top | Give Feedback

STATUS

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

This problem was first corrected in Microsoft Office 2000 Service Pack 3 (SP-3).

Back to the top | Give Feedback