Now if only it would stop dropping leading zeros unless you ask it, and we got rid of the MM/DD/yyyy date format entirely.
Now if only it would stop dropping leading zeros unless you ask it
That appears to actually be a feature.
Holy shit! Now I just need to talk to some sysadmins and get some group policies set.
Apparently our typical installer for Visio 2016 and our 365 license use "incompatible installers" so it is going to be a pain in the ass for me to have both installed at the same time. Thankfully I'm trusted by IT so I might be able to just do it myself.
I think the point was that the format itself is odd. I am European and it's weird to me: logically it should be either from greatest to smallest, or from smallest to greatest, not a weird in-between.
Now if only it would stop dropping leading zeros unless you ask it, and we got rid of the MM/DD/yyyy date format entirely.
That appears to actually be a feature.
Holy shit! Now I just need to talk to some sysadmins and get some group policies set.
Apparently our typical installer for Visio 2016 and our 365 license use "incompatible installers" so it is going to be a pain in the ass for me to have both installed at the same time. Thankfully I'm trusted by IT so I might be able to just do it myself.
Edit: Looks like I'll need IT after all. https://learn.microsoft.com/en-us/deployoffice/use-the-office-deployment-tool-to-install-volume-licensed-editions-of-visio-2016
MM/DD/YYYY is the correct format here in America.
I think the point was that the format itself is odd. I am European and it's weird to me: logically it should be either from greatest to smallest, or from smallest to greatest, not a weird in-between.
Logically it would be milliseconds since 1970.
Not very good for birthdates.