This article discusses Xoom Word Pro for Windows' Y2K compliance.

Compliance Statement

Xoom Word Pro for Windows 1.0 has the following two known Y2K problems:

  • The template macro (template.xmc)
  • The Insert | System variable | Date mail merge variable
  • The Insert | System variable | Date as Text

Will these problems affect you?

That all depends on whether or not you use these features.

  1. If you use the Calander Template then the template macro problem will affect you.

  2. If you use mailmerge with date variables, or two digit year numbers, then the date merge problem will affect you.

    1. Xoom Word Pro for Windows will report the century as 19xx.

    2. Two digit years lower than 10 will not have the leading zero.

    Inserting the date as text will show the same effects.


To provide the maximum level of Y2K compliance you should apply three corrections, as detailed below. Xoom Word Pro for Windows 1.0 will still not be fully Y2K compliant, but the corrections detailed should allow you to work-around the remaining issues.

Article Q1030 describes a replacement for the template macro.

Article Q1031 describes a patch for XMWIN.DLL that overcomes most of the insert date Y2K problems. This patch will not correct for the missing leading zero for two-digit year numbers inserted as text. To overcome this problem you should also see article Q1029.

Article Q1032 describes a work-around for the date variable - by inserting it as static text. This is the only way to completely correct the date inserted as text Y2K problem.