I am having problems with my 21st century dates getting converted to 20th century dates! This will be lethal to my application, as it is a scheduling system!

Are there special rules for dealing with Year 2000 dates in ViP? Please give me any information you have, as I am having problems in the immediate.

Thanks,

Ken Wachs

Please read the link titled "Year 2000 Compliance" in the "News & Info" section (see left panel.) If you are not using ViP2.5 (particularly before release 2.2) there may be some problems that were fixed in a later release. If you are having a specific problem doing something, give details.

John:

Thanks for the info. I have read through the Year 2000 docs, and ViP still does seem to be behaving a bit strangely.

According to the docs, a date entered with two digits (e.g. 5/8/08) will be assumed as being in the 21st century if the year number is less than 50.

But when I enter dates like this (as an example 1/1/00 or 2/5/01), the date is saved to the data object as 1900 or 1901?

For the moment I have gotten around it by passing every date input by the user through a sub of my own (Year2000Date). For my purposes, the code translates anything < 96 as a 21st century date. We have no data older than 2 years.

This may warrant some investigation. I am not changing the date in any way (I don't think).

Anyway, I just thought I'd let you know.

Regards,

Ken Wachs

Hmm. Are these dates fresh or dried? Are they pitted? Does this happen with any mid-eastern fruit? How about frankensence and mirth? If you hold your breath for a real long time, does your face turn blue? If so, breath. If you breathe deep, be carefull, you should be breathing air.

Gary Gnu

View this thread on the forum...