Posted on

Microsoft Office Genuine Disadvantage

In April 2008 Microsoft released a ‘needed’ update for Microsoft Office 2003 (and, I believe, XP and 2007). The only purpose appears to be to check if the software installed no your machine is “genuine”, at least as far as Microsoft is concerned.

In typical Microsoft style, it didn’t always work. I’ve noticed it popping up nag screens on machines I know where running genuine software, as supplied by major OEMs. Microsoft famously had the same problem with Windows XP Genuine Advantage, resulting in a certain major mail-order PC supplier’s machines having problems. Microsoft’s servers have also suffered faults, disallowing thousands of copies of their software for no reason whatsoever.

Latterly I’ve come across several machines running Office 2003 having problems. This used to be a worrying nag screen, but in the last couple of weeks I’ve heard about genuine software being deactivated in early April. Whether this comes about remains to be seen!

I’m not clear as to why this is happening. Is it a bad de-install of Office 2007 causing the problem? It seems to affect Vista machines which were pre-loaded with Office 2007 and moved on to site licensed versions of 2003 (because everyone hates 2007). It may also be interference caused by malware modifying Office 2003.

One worrying prospect is that Microsoft is unable to manage licenses for this old product and has simply messed up.

Basically, installing anything that might decide you’re running a pirated software and shut you down is a fundamentally bad plan, and best avoided. If you decline these “needed” updates it will prevent you from installing new features (other than critical security fixes) but you can carry on as normal. The risk outweighs the benefits.

Microsoft’s trend has been to restrict the installation of its software for many years, which is a disaster if it doesn’t work. It’s yet another reason for people to switch to the open source alternatives, such as OpenOffice. The cost of the licenses from Microsoft doesn’t bother me; it’s the risk of the self-destruct code they’re building in. If you’re a large corporation you can probably drag Microsoft in and tell them to fix it pronto, and pay compensation. It’s the small guy’s who’ll suffer.

Posted on

Sage 2011? Line 50 with a proper database

Today I ran in to my “old friends” Sage at a computer show; they didn’t recognise me and tried to interest me in Sage Accounting for my business. I was wearing a suit, I suppose. As you can imagine, it didn’t take long for them to catch on, after which I turned the subject to the subject of Line 50 using a proper database.

You might have got the impression I really don’t like Sage. That’s not strictly true; the issue is that I really don’t like the idea of Line 50 being sold to SMEs planning to use it for anything non-trivial. Interestingly, the people from Sage agree – at least in private. The database driven version to cure the problemhas been promised for four years, so they’re obviously aware of the issue!

So when’s it coming? Apparently in Sage 2011, due out in August 2010. “Really?” I said. “Yes, definitely. At least that’s the plan”, they said.

I pushed a bit further – would it be using mySQL as promised or would they wimp-out and use the lightweight Microsoft server. I didn’t get an answer, which confirms my fears, but even a Microsoft SQL server is better that the current arrangement.

I tried to discuss the performance issues for people upgrading to Line 50 Version 2010 with them, but I got the impression they were a bit jaded on the subject, and did a very poor job of feigning surprise.