>A lot of my apps only show and print the date as held in the dbf. If the user
>enters 01/15/03 then the computer stores it as 1903. But that's ok because when it
>prints the date it still prints 01/15/03 and it will appear to be 2003.
Yes, but if you have any date indexes, they will sort improperly. Do
you have any reports that print by date range? Broken.
>For the date fields that can potentially be used for calculations, such as
>invoice date, after reading the date from the user I have the following
> InvoiceDate = InvoiceDate + 36525
This won't work after Feb 28, 2000, since 2000 is a leap year and 1900
is not, leaving your formula one day off. It will also always
calculate the day of week improperly, even if you correct that offset.
Day of Week repeats every 28 years until 2100.
Better to use the Epoch function for S'87 available on my www site.
>Also, I have found that for a pc that will keep the proper date after Y2K, then
>Clipper responds to the DATE() function properly...
>Does anyone see any problems with this logic?
Well, Fred, if it were me, I'd catch those input dates and correct
them before storing them. After doing that, everything works pretty
much as expected.
There is some patch code on my www site that addresses this and other
problems. Also, read the links on my y2k link page.
Oasis WWW http://www.iag.net/~philb/
Oasis WWW Mirror http://www.enterconnex.com/oasis/
FTP Site ftp://ftp.iag.net/pub/clipper
Everything that is really great and inspiring is
created by individuals who can labor in freedom.