OL97: "Type Mismatch" Error Message When You Export to Timex Datalink (251237)
The information in this article applies to:
This article was previously published under Q251237 SYMPTOMS
When you export data to a Timex Datalink watch for any date that is January 1, 2000, or later, you may receive a "type mismatch" error message.
CAUSE
This problem can occur because Outlook pre-populates two date fields in the Timex Datalink portion of the Import-Export Wizard. If you export the current time and date, the day of the week is not correct because Outlook calculates the day as if it were the year 1900.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Office 2000 service release that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English-language version of this fix should have the following file attributes or later:
Date Version Size File name Platform
-------------------------------------------------------------
1/12/2000 2.00.00.0001 320,000 Outltimx.dll 001033 English (United States)
WORKAROUND
To work around the problem, press the button on the watch to set the current date and time. The watch automatically recalculates to the correct day.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 10/6/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbfix kbQFE KB251237 |
|---|
|