🚀 go-pugleaf

Tim Foster wrote:

>After some testing in a VB4 16-bit application, I'm fairly positive there
>is a problem reading dates into Variants (VB seems to be trimming the dates
>to Short Format), and so when the Year 2000 rollover occurs, the dates take
>on '20' as the century value if you read values back from the Variant.

I think you worry too much.

What you are looking at is the PRINTOUT FORMAT of the date, not the
actual date itself. Try using Format$() to get proper 4-digit years.

Internally, VB stores dates as day numbers (since 1900 or something),
with fractional parts for hours/minutes/seconds. One hour is 1/24
(~0.04167). See VB help, DateSerial(), for some more info. Just for fun,
try printing the result of applying CDbl() on a date.

As long as no part of your program actually depends on the date as a
string, with the year in two digits, you should be pretty safe. I just
hope the Access stores the dates properly.

HTH,
Bart.