Using a Single Digit for a Year

@jamies
I agree with you. What is the purpose of this requested date format? To confuse consumers? or to be able to sell a product that is over ten years past the expiry date?
Also, there are product that have very long shelf life, for example plastic drums and other containers, but they do age, and should be replaced after expiry, often 5 to 10 years after production. Such date format would have been useless for those.

What's wrong with MOD(YEAR(date),10)?

Then again,
perhaps it is wise to consider -
Should you use a single digit for a year ?

indeed, for those who were involved in any computing activities way way way back in the year 0
OK, 2000 AD,
Think about all the problems reported, and encountered, that were considered to be the "Year 2K" effects -

the Effect being of all those computer systems set to only use 2 digits for the year,
so computer systems calculating things like interest on a loan taken out in 1998 as having 97 years interest due in the 3rd year of the borrowing.
and the people born in the early 20th century being told that, as a minor, they needed their parents permission to do things, such as not be at school.

Oh - and please remember Windows is coded to handle dates entered as 2 digit years as being either in the 20th century, or the 21st century depending on the value being over (is it 35) so a date with a year entered as 40 precedes one entered as 30.

My suggestion is an user defined function:
```

Public Function DateCode(DateVal As Date) As String

DateCode = Format(DateVal, "mmdd") & (DatePart("yyyy", DateVal) Mod 10)

End Function
```
You can add a check whether argument is a valid date. The result is a string, but can be easily modified to a number; however it cannot be a date.

Also the code generated will be off by one day for dates between Jan 1 and Feb 28, in the year 1900. BTW, Excel accepts Feb. 29, 1900 as a valid date while 1900 was not a leap year; the code will be off by one day for that invalid date too. This shouldn't matter for Bruce though.

I use and would love to see a universal date format of yyyy-mm-dd.
This puts folders and files in chronological order even where the system is not seeing it as a date.

Using dashes instead of slashes allows this date format to be used in file names. I use this as a simple method of version control.

It also has the advantage of conforming to ISO 8601. If nothing else, conformance helps eliminate the "mine is better than yours" argument.

Lastly, this format seems universal enough to be recognized all over the world. It's worked so far for the people on the four continents I work with.

VBA also has a nice little DatePart function. In the immediate window, this input "? right(DatePart("yyyy","01/16/2021"),1)" produces a result of "1".

I use and would love to see a universal date format of yyyy/mm/dd. This puts folders and files in chronological order even where the system is not seeing it as a date.

Seems terribly logical.