Re: JBA Year 2000 Compliance

[Jim Sehi <jsehi@xxxxxxxx>]

We are close to implementing 3.5.0 and have not (to date) experienced any
Y2K issues with the software.  There are several areas that do have
problems... one of which is the TP module which JBA has acknowledged is not
Y2K compliant.  There is also one FIPxx record lock file where the lock
date is still 6 digits... but other than that... we are keeping our fingers
crossed.

We have been assured by JBA that the other systems (ie. MRP) are compliant.
 Have we done Y2K testing on the software?  The answer to that question is
"NO"...

******************************
Jim Sehi
Sr. Programmer/Analyst
Hach Company
5600 Lindbergh Drive
Loveland, Colorado  80538

Email:  jsehi@hach.com
Phone:  970-663-1377  x2538
Fax:    970-669-2932
******************************

At 09:33 PM 7/15/98 -0400, you wrote:
>Does anyone have any testing experience with V3.5.x and Y2k?  We are
looking to upgrade from 2.4.1b to 3.5.x and want to confirm that all Year
2000 issues are resolved.  Database compliance is not an issue even in the
version we have, but there are programs in manufacturing, for example, that
were not compliant through 3.4.3.
>Thanks for the help,
>Bruce Stern
>sternb@erols.com
>
>
>Attachment Converted: "g:\inetmail\attach\JBAYear2"
>
******************************
Jim Sehi
Sr. Programmer/Analyst
Hach Company
5600 Lindbergh Drive
Loveland, Colorado  80538

Email:  jsehi@hach.com
Phone:  970-663-1377  x2538
Fax:    970-669-2932
******************************

+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---