CodeSiren
New Member
- Joined
- Sep 6, 2012
- Messages
- 82
- Reaction score
- 1
I have always assumed it was something with older records because in my brother's case, it seems that's where it showed that way....but I don't know that to be for sure. That said, I've seen it too many times (with other people as well) to think it's a simple typo. It has to be some sort of default date or something and whatever the reason, it is far from unique to this case. Same exact date is on many, many other records.
Chiming in as I'm a software/database developer. An archaic, obsolete, and inefficient way of handling null and/or default dates way back when was to use a specific value when loading bulk or single records. Particularly an uncommon value, such as this 1950 date. That way they could filter on that date value, whether for inclusion or exclusion, and didn't have to worry about null values. The government is hopelessly behind on technology and still frequently uses outdated constructs such as this. This is just an educated guess based on experience - I don't know if its actually the case here.
ETA: posted before I saw NJ's post