I'm currently trying to convert a MS Access table to a SQL Server 2005 table. The problem is that there are dates that Access has that SQL Server can't handle. Weird, huh? SQL Server is supposed to be more powerful by far, yet Access can understand dates back to 1/1/100 while SQL Server can only handle dates back to 1/1/1753. Why? Who the hell knows. One person suggests that 1753 is when Britain adopted the Gregorian calendar, but it was actually 1752 and the calendar has been in use since 1582/3 by Spain, France, Austria-Hungary, Portugal, Italy and most of the rest of continental Europe. The "genius" making this statement says Spain and France had been using it for "Some Decades" before that. Sure, 20 decades.
He later goes on to state
But then dates back then are not necessary to have the precision of a datetime column. Even more recent dates, think of something closer to your home the discovery of Australia by Europeans (the Dutch, I believe) was in 1606. Do we know the month even? I don't know. Is it relevent? Probably not. I mean by who's callendar. The Dutch calendar? Were they already using the adjusted Gregorian calendar or were they still using like the British the Julian calendar? I don't know.
But you can see how dates are fairly meaningless before 1753, at least in any precision.
Yeah, no-one really knows when anything happened before 1753, did people even write back then? Moron.