Yes there is a product that deals with Y2K issues without changing the data
from 2 to 4 digit years.

<<plug alert>>

Millennium Rx is a series of tools that allow programs to continue running
after Y2K without making program and data changes.  Sort2000i and Sort2000x
are sorting tools within the product that handle the sorting problems caused
by the 2 digt year after the year 2000.  Both external and internal sorts
are handled simply by running existing code with our XL.  DBImage2000 is
another tool in the product that will intercept Image calls passing back 4
digit years or 2 digit years.  This is useful for programs that need to have
logic changes made based on 4 digit years but the data is stored in 2 digits.
It can also be helpfull for programs that still are programmed for 2 digit
years (as they have no need to change for 4 digit) but the data is stored
in 4 digit.

Our whole Y2K philosophy is to allow programs to continue working after Y2K
without incurring costly code and data changes.

For more information please contact Gordon Croston at Genesee Software by
phone at 1-800-728-9123 or e-mail at [log in to unmask]

<<end of plug alert>>
>On 10/27 1997  "mdc.com (Joseph Uhrig)" <<[log in to unmask]> wrote:
>
>Folks, Is this really the place for this ?  I just joined this list in
>the hope of finding a robust discussion of Y2K problems and
>approaches.  You could say that I'm much more interested with how
>folks are dealing with byzantine data, file and program relationships
>than byzantine (and fractious) text interpretations.
>
>My shop has a multiple language enviornment and because of the
>expected life of our systems, the structure of our data, and the way
>our dates are used, we have decided to utilize a date windowing
>approach.  Basically we're avoiding date expansion except as a last
>resort.  Almost all our dates are in YYMMDD format and we're using
>standardized date routines for conversions, comparisons, edits,
>calculations, etc....  We're adding seperate century fields in Image
>for those dates that are used as Image sort keys.  This approach is
>working quite well for programs written in Transact and Cobol, but
>unfortunately it makes our adhoc reporting a little more difficult.
>
>Are there any MPE/iX products out there that  allow conversion on the
>fly of YYMMDD dates for sorting and comparision without having to make
>multiple passes thru the data?
>