ACSLWhats NewAbout ACSLProductsDownloadsServiceSupportPress ReleaseE-mail Welcome to ACSL
ACSL is committed to ensuring all of our software products are year 2000 compliant. The year 2000 problem has received a lot of press lately, and will continue to as the beginning of the new millenia approaches. For many companies and governments, the problem is significant because of the amount of very old programs being run on mainframes, minicomputers and personal computers. This problem particularly plagues older mainframe programs, and is an even bigger problem because of the age of the software and the number of occurances of dates within millions of lines of code.

This can represent a tremendous challenge in technical resources. Fixing the year 2000 problem is actually quite trivial as a programming problem, and there are a number of published methods ranging from changing to a 4 digit year, to reinterpretation of existing 2 digit years. While simple to fix on a case by case basis, it is the number of times the change must be made, and the checking of secondary routines that rely on one particular date format or another that makes it a daunting task for some organizations. To further complicate matters, very old mainframe programs are no longer supported by the original suppliers and programmers, and in some cases, even recompiling the original source code represents a massive challenge.

ACSL are Y2K Compliant

The following ACSL products have been audited and are Year 2000 Compliant and Ready:

  • Solution System 2 Version 4.60 or higher

  • Visual Practice, Any Version

  • CaseBASE Version 3.0 or higher

Y2K Compliant means our products faithfully accept, store, calculate and manipulate dates with 4 digit years correctly. 

Watch out for snake-oil salepeople!
   

We have observed that many unethical companies and/or sales people are exploiting the fear of the year 2000 problem as a sales tactic. Keep in mind that for them to submit and reconcile to and from the Ministry of Health, they would have to use 2 digit years in their submission and reconciliation routines! If they didn't they wouldn't be OHIP compliant! They will also have to modify their software based on the new Ministry of Health specifications. We have spoken with several of our customers who have been approached by sales people claiming that they need a new software package to be year 2000 compliant and that we don't intend to update our programs. This is a predatory, unethical, lie, designed to make you spend money on their product.

You do not need to buy any new software to ensure year 2000 compatibility if you are using an ACSL software product. Any sales person who tries to convince you otherwise is either totally misinformed or is outright lying.

If you have any questions about this issue, please feel free to contact us.

©1998, Advanced Computer Systems Limited