Article ID: 319295 - Last Review: April 29, 2003 - Revision: 2.2

WD2000: Swedish Grammar Checker Stops Responding If You Type Date String That Does Not Contain Blank Spaces

View products that this article applies to.

This article was previously published under Q319295

NOTE: The information in this article applies to the Swedish version(s) of Word 2000.

SYMPTOMS

The Swedish grammar checker may stop responding if you type a string that is a date without blank spaces, such as 23mars2002. You may receive an error message similar to the following:

Winword.exe has generated errors and will be closed by Windows. You will have to restart the program. An error log is being created.

Back to the top

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 Swedish version of this fix should have the following file attributes or later:

   Date         Time   Version   Size       File name
   ---------------------------------------------------------- 
   12-Apr-2002  18:26  n/a       1,205,760  Msgrsw.msp
   12-Apr-2002  18:36  n/a       1,292,800  Msgrsw_admin.msp

After the hotfix is installed, the Swedish version of this fix will have the file attributes (or later) that are listed in the following table. 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
   --------------------------------------------------------  
   09-Apr-2002  14:58  1.0.1.8     856,064   Msgrsw32.dll     
   13-Nov-2001  19:35  n/a       2,728,382   Msgr_sw.lex

Back to the top

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