Monday, 13 December 2010

More VB and SQLWoes

I promised I'd keep readers up to date with my Visual Basic project issues, here's another one:

Problem #4: MS SQL Server has a base date of 1752!

Why is this a problem you ask? Because I've decided my VB project will be my Access family history database. I can trace my family back to the 17th century, long before 1752.
Why 1752? That is when the UK and US switched from the Julian to the Gregorian calendar, and also moved the legal year end ffrom 31st March to 31sr December. Dates before that can be problematical and SQL Server's progenitors evidently elected to simply not allow earlier dates.

This isn't quite a restrictive as MS Excel which won't handle dates before 1900, but Access happily goes back before 1752.

It wouldn't be hard to permit any date - what do historians and archaeologists do?

No comments: