OK - here is a better explanation - this should clear things up.

http://en.wikipedia.org/wiki/Gregorian_Calendar

http://en.wikipedia.org/wiki/Julian_calendar



>It is based on the Julian calendar in that it consists of a solar year of twelve months and of 365 days with an extra day every fourth year (well sort-of). :0) One could argue that it was an improvement on the Julian calendar since the Julian calendar existed first and accumulated errors or the error grew until every 130 (?) years the calendar became out of sync or wrong. With the Gregorian calendar the rules became rather convoluted - divisible by four, not divisible by 100, or divisible by 400 or something like that! They moved Easter and the extra day was moved to after Feb 28th.
>
>Perhaps someone who knows more can write it better! :o)
>
>
>>Actually the modern day calendar is the Gregorian calendar.
>>
>>>>>The birth dates are the 14th century of which calendar? This is the problem with storing dates before 1753. One solution is to store these dates as a number of years before X date. It means another column in your table and that the DTS transformation will have to contain some activex script - or - use a VFP view that splits it up into different columns. You won't be able to perform any datetime arithmetic on these dates, but without the precise calendar information including manual adjustments and leap days, any datetime arithmetic is meaningless.
>>>>
>>>>The present date calendar, I mean the one we regularly use, is known as the Julian calendar. Isn't it?
>>>
>>>Yes, but the Julian calendar is not continous before 1753. There are adjustments that have varying lengths and occur on different days depending on your locale. Some countries had different calendars and some countries were simply on a different day.