Year 2000 compliance for RevG - and don't laugh (OpenInsight Specific)
At 04 NOV 1998 01:27:14PM Jeff Word wrote:
We need to know if the RevG development system and runtimes are Y2K compliant. We know this goes way back, however, we will have several customers that will still be in RevG into the year 2000.
We know that the Julian dates will be fine. Are there any other parts to the software that will have issues?
Someone mentioned to us that some software made direct calls to the system clock. Do you know if this applies and if this is an issue with RevG? All comments welcome. (except if you are going to make fun of our customers)
At 05 NOV 1998 04:28PM Steve Smith wrote:
REVG's date ICONV may not handle the way you expect it to for year 2000. Try enering a date in a screen field with a 2 character year=00 and then save it and then view it to see what you get.
REVG's calls to the system clock are standard calls, and should not be a problem. There are third-party patches in existence for REVG's ICONV routine.
In future post your message in the AREV Specific category - it will reach more REVG-familiar ears there.
Steve