I was writing off an amount in the customer module but managed to write off the whole balance on account. I have tried to delete the write off but SAGE is showing me this warning message, "This transaction has a reference marking it as reversed, therefore this change cannot be allowed."
Is there anyway of getting around that? I haven't backed up the system for 2 weeks now so restoring the old data is my last choice.
1) Restore your last back-up and re-enter all your work since that point. (It's possible to imperfectly short-cut this, greatly reducing the amount of work necessary, but it's a long-winded explanation, so personally I'd go for option two...)
2) Manually reverse the write off / recreate the original transaction. i.e. look at the write off in the audit trail, and post something that does the opposite.
In addition to those two possibilities, there is another thing you really must start doing: Which is take more regular back-ups. My recommendation is to take one at the end of each day (or session) in which Sage is used - i.e. take a back-up whenever Sage is quit.
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
Sorry you learnt the hard way - back ups are so important hence sage always warning and asking the question. I always advise if trying something new or unsure of entry - Take a data back up - it only takes minutes but saves a lot of additional problems.
__________________
Donna Curling - Complete Book-Keeping Ltd (CBKLtd) - 07939 101900
Sadly, my experience is that people only learn the importance of back-ups when the lack of adequate back-ups rears its ugly head and bites them in the bum - ie when a disaster strikes.
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
I was at university, writing a year-long project using a Sinclair QL with attached external 3.5" disk drives. The QL worked fine, but the disk drives had a tendency to overheat if used for too long, and one side effect of this (as I was about to discover) was to corrupt the FAT (indexing tables) for the floppy disks.
So one week away from handing the project in, it doesn't load any more. Had I bothered to use two floppy disks and make copies on alternate days? No. Did I have printouts of intermediate work? No. Did I even keep copies on those fiddly microdrives the QL has which I wasn't using because I thought 3.5" floppies would be safer? No.
In fact, did I have any kind of backup at all? No. And yet, how simple any (or indeed all) of those would have been to do!
One panicked week later I had rewritten my entire project from scratch and submitted it. During the summer, when I had written some software to read the sectors of floppy disks directly and managed to manually patch together the files, I was able to compare what I had submitted with what I had lost, and one of only two good things which came out of that whole mess was that the project I rewrote was better.
The other, of course, was the lesson learnt: to take regular backups on different sources. As I have done ever since.
And to date, I have never lost anything else due to failure of a computer, an accessory, or my stupidity.
It is easy to do. Sage is say the reference "BADDBT" I think is marking it as reversed. So Edit and change the reference to something innocuous ("MyError") and save. Now you can delete the entry.
