Wednesday, November 16, 2011
Manifests in VB6
Tuesday, October 18, 2011
Inflation - time to do some sums
Wednesday, October 12, 2011
Jobs - what jobs?
Tuesday, October 11, 2011
CLOUD = Complete Loss of Your Data
Friday, October 07, 2011
Changes...
Necessity may be the mother of invention but discontent makes the world go around.
Without a niggling feeling of general unhappiness with out lot most people would do nothing to change their lives.
If you are fed up with the weather in your current area you can choose to just accept it, constantly whinge about it or do something about it, which will most probably result in moving to another region where the climate is allegedly more in line with your desires.
The accepting types form the stoic background of our societies who can be depended upon to quietly accept whatever iniquities whoever is currently in power decide to burden them with, just don’t expect much from a group who are largely content with a nice comfy pair of slippers and a yellow cardigan with leather buttons.
The malcontents are frankly just a pain in the backside. Meet them in ten years time and they’ll still be going on about the same objects of their discontent but with some embellishment as to why they haven’t actually done anything.
Those who actively make changes in their lives for whatever reason are the drivers of the world. They make something happen. The “something” may not always be the desired result but without it we only suffer from stagnation.
In a perverse way it is probably the plodders who are most content in life. Those seeking change are quite likely to be always looking for the greener grass. The knowledge that you can change your world is a powerful and sometime destructive force.
Monday, October 03, 2011
Pension off the Pension
Monday, July 11, 2011
Sage 2012
Sage Line 50 2012
We have been using the Beta copy of the software and also attended the Sage dEvent that provided an overview of what’s new and changed in the 2012 version.
Although Sage haven’t changed the underlying file system they have made changes to how Sage caches data and tried to improve the locking mechanisms so that some operations will no longer lock out all the other users.
Our initial speed tests show no overall difference (possibly a bit slower) on straight speed but the record locking and caching may make day-to-day operations less prone to other users being locked out and support higher levels of concurrency.
The cosmetic screen appearance has been updated to make it more contemporary and various processes modified to give the user more feedback that Sage is actually doing something (rather than having them reboot the machine because nothing is apparently happening and thus corrupting data).
Data can now also be “locked” so that transactions can’t be posted to a previous period which should keep the accountants happy. This is set via User Rights although the default is to allow it which seems a bit perverse.
The Help -> About screen now provides far more diagnostic information and they also seem to have sneaked in a remote control option for Sage Support technicians.
Internally there are changes to the way the SDK works in some areas so developers will need to make code changes in various areas including Net Value Discounts (which was absurdly difficult to do previously), Customer Discounts and Invoice Auto Numbering.
The Transaction Post has also been updated to perform more checks on the data such as making sure the specified nominal code is correct for the type of transaction (not a Bank Account if posting an SI for example).
Installation has been streamlined and made more straightforward for network configuration.
There are various UI enhancements including new Quick Search Options and a Quick Print button.
Data checking has been speeded up and offers more selective repair options than the previous blanket “Fix” button.
The existing SData Service will be available to developers in Beta format. Essentially it is a web interface which sits on top of the SDO to enable low volume web based interrogation and update of Sage data. (You would for example only perform an action on a single account rather than a bulk process)
Overall it’s the same (very) old file system that they have tried to wring a bit more performance out of it by doing things that they should have done years ago but now seem to be taking a bit more seriously. I guess the cash cow needed a bit of feeding.
Let’s hope there isn’t the usual “oops” moment in the first live release. As usual wait and see before upgrading.
Developers Program Changes
Sage are also planning to introduce a Certification program for third party applications.
This will be an annual test priced at around £600 per product.
We certainly won’t be pursuing this option as it would push our Sage fees up to well over £5000 per year. We’re confident in our products and the level of support we provide without entering into essentially what is an expensive box ticking Certification exercise.
Incidentally Sage say they have around 600 Sage 50 registered developers which on current fees I would calculate is generating them around 1 million pounds a year in revenue and must be very profitable already.
Emailing Sage documents
This is something I have never really looked into but a client wanted to do this and so necessitated a bit of investigation.
Short story is that it is possible and very simple to use but a bit less than obvious to set up and of course different depending on the version of Sage you have.
Essentially you need to use the Report Designer to set up the Email Settings which will create a default Email configuration for all reports set to send via Email.
If you are using Outlook choose MAPI otherwise choose SMTP and enter your ISP Mail Server details. There is also an Outlook option that is apparently only relevant for Outlook 2010 on a 64 bit system.
Then for individual reports you set up the email options (such as setting the email address to be picked up from the Sales Account Email field and Subject text etc)
Once set up you can just select the Invoices in the Invoicing Module and click on the Email button (in Sage versions prior to 2011 it is a bit more long winded)
There is a Sage Knowledge Base article 12659 that provides some information. The independent Sage Forum also has a succinct How to on setting up Invoices to Email.
On Windows 7/Sage 2012 at least the SMTP mail configuration appears to be stored in ProgramData\Sage\SMTP\SMTPConfiguration.xml and includes the username and password in clear text, which might not be the most secure way to do things.
Friday, June 10, 2011
Autoglass - Don't
Nothing wrong with the service or the repair - in fact it was beyond reproach. What I couldn't work out is how this could be "free".
Now I know.
The adverts tell you it won't affect your no claim discount. What they don't tell you is that it counts as a claim on your insurance.
Mine went up by £200 as a result.
And I don't expect it will go down again any time soon.
So it is a scam.
Autoglass get x pounds from the Insurance company who then up your premium with no risk to themselves.
Don't do it.
By the way I have complained to the ASA, but I'm not holding my breath.
Wednesday, June 01, 2011
SMB2 or how to corrupt your data without really trying
Deep down they are just a desktop company, bit of Office, nothing serious, mostly works if you are lucky. Good job Dave Cutler came along. Clearly real world issues aren't high on the list probably because they're too busy counting the money and coming up with the next ill concieved way to screw something up.
SMB2 - Microsoft have previous on this whole area but as far as I can see SMB2 will corrupt just about every application that uses file sharing due to caching and metadata issues. Perhaps there should be a new 4 letter word at Microsoft called "TEST". "Think" might also be good. Or just stop "fixing" things that mostly work (or at least we have got used to and know how to workaround).
We are moving into ill considered areas now. What happens when your Cloud evaporates?
There is so much data recovery is almost impossible.
The same applies to large scale systems - the HMRC system is broken and I can't see how it will ever be fixed. It's a live system that we know is wrong that we are adding data to every day. So at best it will be an approximation of our affairs and it will be up to the end user to spot the more obvious errors whilst being told "the computer says no".
Meanwhile all our data is being hacked because even large companies (never mind the small ones) we hand over all bank details to have apparently never heard of the idea of encrypting passwords.
There seems to be a blind assumption by everybody that all this stuff actually works.
It doesn't.
Monday, March 14, 2011
Sage and Windows 7
The good news is it doesn't seem to have the performance sapping cache effect of Vista and performance is much the same as XP (even though it's running on an iCore-5 as against XP on a Pentium P4 2.8ghz. Oh well).
Interestingly, swapping from 100mbit Ethernet to 1gb made almost no difference to our Sage performance test results although a straight 25mb file copy was around 4 times faster.
Monday, March 07, 2011
Sage 50 and Vista - slower than a slow thing
Recently I have been investigating the use of NAS devices with Sage Line 50 and spending a lot ot time analysing the performance using our Sage testing tool, Transfix.
What was strange was that the first run of the test was quite fast, but each subsequent run became slower and slower until it botommed out at about 3 times slower than the initial test.
Odd.
To cut a long story short the problem is with Vista caching the data to RAM.
On the first run, all the data (in this case a 30mb Sage file) is read across the network. Each subsequent run loads more of this data in the Cache until eventually there is no network traffic at all when the file is read ; it all comes from the cache. You can observe this by monitoring the NIC Status and using Task Manager to see the cache grow.
Sadly the Sage SDO is around 2.5 times (60 seconds vs 150 seconds) slower reading directly from RAM than from the network.
The file is only cleared from cache when a process causes the the file to be updated which then restores normal performance until the file becomes cached again. There does not appear to be any way of controlling this behaviour.
I have no idea if this affects other programs but certainly Sage doesn't like it.
XP doesn't have this problem and I haven't got around to testing Windows 7 yet.
Does nobody test this stuff?