>Well I think it's reasonable to store the value as a number. This way, I think it's much easier to add 4 days, for example. I think the C structure for dates and time is the same, ie x days/seconds since ???.
>
>And of course that's why we'll have the year 2038 bug! :)
>
>But I agree that it doesn't make it easier for us programmers! :)
>
>>Funky for sure. Even that would mean the 1,012,001 day since the year 1785.
>>Which when added to that year, would equal around the year 4670. I constantly need to know how many days have elapsed since the year 1785 ;)


Starting in VB.Net, Date will not be store in a Double. This means that to deal with date, we will have to use DateAdd, DateDiff, ... and also means that we won't have the 2038 bug!