List of PC C/S non-compliant products : LUSENET : TimeBomb 2000 (Y2000) : One Thread

List of our non-compliant PC products, home-grown or bought: Agresso x 4 (4.2.4), Albacs, Fixes, Foxpro DB, Project Accounting, ResSearch 4.1.1, Talisman x 2, SMDS, VPN, Novell Netware x 4, Solaris x 2, SunOS x 2, Arcserve x 2, Oracle DBMS 6 & 5, Project History, Quetzal 4 (has 1999 problem!), Timeplus, AIX, HP UNix x 2, OS/2 x 4, SCO V386 Unix , Evaluator, EY/PD Plus, Interscan Virus Wall 2, Powerchute Plus, Solistice Firewall-1, Bank Line, Contracts Tracking, Library, Open VMS, FT Profile, LAN Server, Lan Workplace pro, MAT, MS Exchange, Oracle Case Dictionary, Oracle Designer 2000, Oracle Forms, Oracle Report Writer, Oracle Reports, PC Anywhere x 4, Powerbuilder 4/4 enterprise, Reflections 2, Reflections Mobile, Reflections TCP x 4, Reflections suite for X, Reflections suite for enterprise x 2, Reflections suite for TCP x 2, SQL server, Sytos Premium, Xvision x 3, Bond As well as various products that are compliant with issues.

-- Richard Dale (, October 23, 1998


Good list, shows you're on top of the problem on a personal question: <> Y2K non-compliant are these products? As an example, Windows for Workgroups, which we run on our print server at home, is considered compliant with minor issues because you can't manually set the time in the control panel to 2/29/00 (although the date will roll over properly unassisted). If the BIOS will handle Y2K, the app will...

At what point, in other words, should we be concerned and get out the checkbook or plastic to get new apps?

-- Karen Cook (, October 23, 1998.

That's supposed to be how Y2K compliant....

-- Karen Cook (, October 23, 1998.

Its very difficult to say how non-compliant the products are, we have given them all a test where possible. I think it may range from minor quibbles (date displays) to say start up routines that just fail. Some did crash in testing. Unless you had inside information I don't think you'd ever find out. We have mostly found out from supplier statements, they rarely said what exactly was wrong.

I don't think they would issue a y2k version unless they had to, most would be reluctant to admit fault unless there were real problems. Some suppliers were "proud", for want of a better word, that their product was compliant. Software now usually has so many features that somewhere there is a date dependent process which you may or may not use. Behind the scenes you don't know how it works. In all the software I have looked at (both bespoke or packaged) generally if there was any involved date processing it didn't work.

-- Richard Dale (, October 23, 1998.


It sounds like you're mixing testing and vendor verification. Since I have neither the knowledge or skill to test our off-the-shelf PC apps, I'm hoping to rely on vendor information. What are your feelings on this approach? I know that Symantec has a program due out called Norton2000 which will tell you which PC apps are compliant. Trouble is, it relies on a database of vendor-supplied compliance info. I'd like to hear your opinion. Thx.

-- Mike (, October 23, 1998.

Moderation questions? read the FAQ