Does Visio have a Y2K Problem?

In the last blog I mentioned the joys of Y2K, it seems Visio has a Y2K problem, but there is no rush to tell them, it will not reoccur until Jan 1, 3000.

I have updated the sample table to include these examples.

The Y2K bug? if you look at Times_Minutes, m supresses leading zeroes but mm does not. Compare that to Date_Year_2000, y does NOT suppress leading zeroes.

and the downloads reflect the change. I have included a Word document that lists the examples, the formats and the results. Creating the list was trivial, Visio has a Print Shapesheet and I just selected the User section to print to the clipboard. Paste into Word and run a VBA macro and everything is pretty. (I love VBA, even if it is in Word. 😉 ).

My documentation still needs updating.

John… Visio MVP in x-aisle

Published by johnvisiomvp

The original Visio MVP. I have worked with the Visio team since 1993

2 thoughts on “Does Visio have a Y2K Problem?

  1. Why is this a bug / problem?

    If it is, why isn’t it a problem again in 2100?

    What happens if you use 2001 in your test instead of 2000… same?

    1. Thank you for your comment, it has been a while since I received a real comment. I have just been deleting spam.
      I like to use interesting titles and though true, this one may have been a bit melodramatic.
      The issue is that the year code does not follow the same pattern as the other codes – single character no leading zeroes, double character leading zeroes. It is the same for 2001 to 2009.
      Hours is slightly different because it also deals with 12/24 notation.
      This download is a work in progress, but I wanted to cleanup a few issues to get the first update out and thought Y to K would get some attention.

Comments are closed.