The user despatched one line for a quantity of twelve and looking at the GDN tables the transaction show's correctly but the invoice was raised for a quantity of 5 and the stock shows a GO transaction for 5!!
Now the first line of the order was for the 5 off and that line now shows -5 as the "to deliver" figure, so it would appear that Sage has errored big time.
I went to check data and I see two errors - 1) Allocated stock value is 7 different from transactions. (or something like that) and 2) Quantity delivered is greater then quantity
My problem is that the "fix" button doesn't work, I hate that button with a passion and try to manually correct as much data as possible but sometimes it doesn't seem like it's possible. What does "fix" even mean?! No explanation of processes or actions used just "fix".
So now I have two errors that won't "fix" and I fear are going to snowball into other errors if I sit back and put my head in the sand.
I'm pretty sure this kind of thing happens because people delete and add lines into sales orders and unless the tables are re-indexed before transactions are made it all starts to get ugly. I've noticed this to cause issues in other areas and to me I think why add functionality that is half baked, if it works and is fully integrated then great but it doesn't, like feeding a dog chocolate!!
And while i'm ranting, the Sage Line50 backend is shoddy and unstable, SQL has been around for so so so long it's embarassing that sage are only just getting round to addressing the fact they are selling a product which is fine when you buy it but as your data grows it falls apart. Then to cap it they turn to you and say "maybe you should look at Sage 200"!! My response being "why don't you supply a robust product in the first place".
The error happened on a Vista 32 bit machine and everyone is on version 13
