Hacked Off with Y2K and Software houses
I accept the companies writing their own in house software still have to check for compliance (some financial programs have been running for 20 - 30 years). They work, they do the job so why change them? Fine, I can accept that but the "latest and greatest" versions of software like Office haven't been around for 20 - 30 years so how come there are so many problems?
As I understand it, a lot of Office and Windows has been written in C++. The nature of this programming language means that you don't have to keep repeating code but that you can "share" it and its' attributes with other code. This is how Office works as an integrated package. Because Word, Excel, Access et al all have the same core, it is easier for them to share data and resources. This is what we are told so how come all these additional compliance issues keep arising?
Personally I think it's a case of too much done by too many in too short a time. The fact that it is common place to find beta programs that are "tested" by us users. Only software does this. Would you "beta test" a car that hasn't been fully road tested? I arrest my case...
What now?
Good question! Where do you go to ensure that your system is compliant? I can only offer the following advice...
· Unless you really need to, do not buy any "new" packages until after the millennium. This is to ensure that you don't get a non-compliant program between now and the millennium. Also, watch out for "bargains" of older software that are not compliant.
· Check the web sites regularly to see if there are any critical updates. If so, you will need to download them and unfortunately, if you are a company, you will have to distribute them.
· Create your own test packs to test your software. It is doubtful that every organisation will use every aspect of a package. Care needs to be taken here to ensure that items don't get "missed". This is why you need to carry out your own tests
· Try and keep your computer environment as stable as possible without too many changes. Obviously it won't be static, but check for compliance statements. It is not unreasonable to ask the supplier for assurances of compliance.
· Check web sites wording carefully. You will often find that hardware or software is
Latest Articles