🚀 go-pugleaf

Access stores Date/Time fields as floating point numbers, with the date
as the integer portion, and the time as the fractional portion. Dates are
stored as the number of days from December 1, 1899 (I think). VB handles
dates and times the same way.

Year 2000 compliance is actually a non-issue.... you just have to be
sure that your code can handle a short date format. (The most common
way is that if the Year of the short date is less than "1935", then add
100 to it before you do anything else. Long format dates do not present
a problem.

Enjoy!

Flewis


Tim Foster <TimF@Romtec.co.uk> wrote in article
<01bfa79b$a1ea0060$03ef98c3@novix>...
> Can anyone help provide information on what the status of Year 2000
> compliance is concerning VB3 and VB4 16-bit apps (using Access 2
> databases).
> 
> 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 could probably fix this by storing DateValues in a Double, but I'm
> wondering if the problem can be resolved in any other way, or if this is
an
> 'official' problem.
> 
> Any help will be much appreciated,
> 
> Thanks,
> 
> Tim Foster.
>