After the debacle of Sage 2007 you might have thought Sage would be a bit more attentive to getting things right in Sage 2008.
Sadly you would be mistaken.
Sage have already released 2 hot fixes to correct problems with the Sage Data Objects (SDO) that are used by Sage Developers and Sage products such as Job Costing that integrate with Sage 50.
There are also problems with Bank Reconcilation and Departments still appear to be a bit flaky.
I'm impressed with the speed that these hot fixes have been released but I'd be even more impressed if Sage had tested it in the first place.
As I've commented (ranted) previously, it's impossible to release a new version every year that actually works. This doesn't fill me with confidence that the forthcoming transistion to using MYSQL as the backend will work before hell freezes over (despite the effects of global warming).
The technical issues with just getting MySql to install on over 100,000 user machines without falling over are immense, never mind porting the whole of Line 50 to use the new technology. Support just doesn't bear thinking about.
Sage hasn't changed the underlying technology since it was first released a very long time ago. Sage users are by and large a fairly docile lot who are just trying to get the job done. 2007 will have tried their patience, 2008 is likely to try it a bit more and start them thinking about what they are paying for.
As usual the best advice is not too upgrade until you have to.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment