Ah, so limiting! I mean what if you were wanting to track the history of some caveman born in 10,000,000 BC . . . I mean, could it really handle that? <g>

March 18, 10,000,000 BC Grog is born.
July 20, 9,999,982 BC Grog writes his first Hello World program in FoxPro
January 12, 9,999,978 BC Grog becomes president of his local FoxPro Users Cave Council


>Dateime in SQL Server is stored as two 4 byte integers. The first 4 bytes store the # of days from base date 01/01/1900. The second 4 bytes store time portion in 1/300 seconds after midnight.
>
>>What date is returned, 01/01/1900 or 12/31/1899? An offset? Do you mean they are stored as numbers, similar to what VFP does? Would that mean 01/01/1850 would be some negative number, internally?
>>
>>Dates are kind of a pain when you get down to the nitty gritty, with issues like the Gregorian calendar change, leap years, all that mess with traveling at the speed of light and how that affects time, etc. I'm always having to change the system dates on my computers when I get back from a cruise through the outer galaxy, you know. <g>
>>