VB3 & VB4 16-bit Year 2000 Compliance Query

Article View: comp.lang.basic.visual.misc

Article #404

Back to comp.lang.basic.visual.misc Previous Next

#404

From: Tim Foster
Date: Thu, 16 Apr 1998 00:00

19 lines
1262 bytes

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.

Technical Details

Message-ID: <01bfa79b$a1ea0060$03ef98c3@novix>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 110e3b,cf6962aa78a8c295,start
X-Google-Attributes: gid110e3b,public
X-Google-Thread: 108062,cf6962aa78a8c295,start
X-Google-Attributes: gid108062,public
X-Google-Thread: f7a67,cf6962aa78a8c295,start
X-Google-Attributes: gidf7a67,public
From: "Tim Foster" <TimF@Romtec.co.uk>
Subject: VB3 & VB4 16-bit Year 2000 Compliance Query
Date: 1998/04/16
Message-ID: <01bfa79b$a1ea0060$03ef98c3@novix>
X-Deja-AN: 344636290
Newsgroups: comp.lang.basic.visual.misc,cz.comp.lang.basic.visual,microsoft.public.vb.bugs