Jim Alton wrote:

> Can anyone give reasonable assurance the 'current' version MM/3000 is
> going to store dates with the HpDate windowing technique where 000101 > would be January 1, 2000 and A20101 would be January 1, 2012?

HP's ISG site in Greeley has been using the latest MM/3000 (Y2K
compliant) version, HP32260C.00.00N, since April and I can assure you of
two things...

1.  It does use a combination of windowing and encoded dates.  If it
encounters a date that is in the "00...." range, it will convert it to
an encoded date based on a windowing scheme of >49 being current century
(19xx) dates (and correspondingly < 50 being next century dates).  If
any data in a record is modified, the date fields (in encoded format)
are automatically posted to the database to prevent the future need for
windowing on those particular fields.

2.  An encoded date of "A20101" would be 01.01.2002 (NOT 01.01.2012)!

Also, any dates that read in from other systems via the standard
transaction file can continue to use "00...." date format and they will
be correctly intrepeted via the above windowing technique.

I know because I am the contractor who did the upgrade and installation
of the Y2K patch - and who has been responsible for tracing and fixing
any bugs since that time.  Fortunately, the software has proven to be
extremely reliable with no real bugs - only some pesky little gotchas,
particularly with date fields that are displayed on inquiry screens.

Glenn
--
 ______________
|  Navigators  | Under contract to Hewlett-Packard ISG (Greeley, CO)
|     |)       |
|     | )      | Glenn J. Koster, Sr.             [log in to unmask]
|     |  )     | Managed Business Solutions    http://www.mbsnav.com
|     |   )    | 214 S. College, Suite 201              970 350-5337
|     |----    | Fort Collins, CO  80524                970 224-1016
| ============ |
| \__________/ |
|   of Change  | aka:  [log in to unmask]
|______________| home: http://members.aol.com/MichiTex