Leonard Berkowitz says:

> We have encountered a problem now that we are using Y2K compliant
> dates, if
> we request a date 777 months in the past (that's 65 years for
> those without
> a handy calculator <g>). The date returned will be in the 21st Century:
> 2033 instead of 1933.

Sounds to me like OCS took the easy way out --- set a cutoff year.
Microsoft did the same thing in current versions of Win95 and NT.  Their
cutoff is "50".  00-49 is considered in the 21st Century (2000-2049) and
50-99 is the 20th (1950-1999).

A simple mathematical equation in a subroutine, and voila - you can keep
your six digit years and cross 2000 easily...  A lot of companies and
vendors are doing this.

(BTW:  Microsoft will be truly Y2K compliant very soon --- the "cutoff" was
a stopgap - which it should be - and not a true solution to the Y2K problem)

Best,
Joe