Ronald wrote:

>             Pad(IntToStr(MonthOf(Date)),2,'0')+

I'm sure it is good enough for the purpose. I suspect a GUID would be easier, but doesn't matter.

One thing that it does do is leak information, and while that might be useful, you need to consider it in terms of GDPR etc. One of the things I used to do was use the current date/time as salt in password hashes (best practice says use a proper cryptograph value now), and that was fine, but I realised it told people the time of the account creation if it leaked. So I changed it and added a random amount of days to the current time, so you have "sometime within a year" rather than specific.

A GUID on the other hand leaks nothing. (In the old days, part of the GUID was the machine MAC address, and they changed that to ensure it was not reversible too.)

Just mentioning it so it can be in the back of the mind in case it comes up sometime.

--

Matthew Jones