Had to test this out of curiosity. Indeed, when using 2-digit year, that is the
result, as expected and explained in the dictionary entry for centuryCutoff.
But how far does the 4-digit conversion work? Here’s what I’ve found:
- On Windows 10, it works until year 3000, and stops working on year
That's the centuryCutoff in action, but I think something is amiss since
it's only supposed to apply to 2-digit years and you supply a 4-digit year.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On November 6, 2022 8:28:34 PM Mark Clark
That's the centuryCutoff property in action, but it's only supposed to
apply to 2-digit years. So I think something is amiss since you supply a
4-digit year.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On November 6, 2022 8:28:34 PM
I was testing one of the tools I use to handle licensing today and decided to
run the series through a few iterations adding 2 years at a time. I noticed
that my dates were reverting to the 20th c. Hmm, whoops.
After a bit of head scratching I decided it wasn't just my doing.
Date conversion
