Page 1 of 1

Corrections Not Saving

Posted: 17 Nov 2008, 13:08
by Bronson
Hi there,

I teach Sage Line 50 v12 at a London FE College and a student brought up a problem which I cannot solve. I have kicked this upstairs to the IT Manager, and he cannot sort the problem either. :cry:

The Problem:

If somebody charges a purchase invoice to the wrong supplier, it should be straightforward to change the wrong supplier account to the right one by doing the following:

File
Maintenance
Corrections
Find and highlight the wrong PI transaction
Edit
In Details, select the drop down menu, change the supplier to another
THEN Save.

Unfortunately, when we click on Save, nothing happens!

I spotted this fault on one of the networked classroom computers. I then tried this correction at another workstation in another room and it worked! By the next day, it no longer worked.

On my office workstation it did work until today.

My guess is that there has been some sort of update that is interfering with the ability to save the changes.

Oddly, if I change other things. like the invoice number only, then it will save without any problems.

The IT Manager has tried taking off all restrictions on permissions and it is still not working.

Has anybody any idea what is wrong, or how we can go about getting the corrections feature to work again.

As an aside, he took home a copy of Sage Line 50 to install on his own home PC to see if the feature would work there, where there were not the same applications as at College and it is not working there either!

Help!

John

Solved! I think!

Posted: 19 Nov 2008, 13:59
by Bronson
It would appear that if you open the Demo Data in version 12, and then go to File/Maintenance/Corrections and then select a PI and try to edit the supplier it will not save. However, I tried this with a file from v10 which I converted to v12 use, and it works i.e. it is possible to edit a supplier to a posted PI. I wonder why the demo data will not allow the change?

John

Stop Press!

Posted: 19 Nov 2008, 16:03
by Bronson
Further to what I have written, I got the IT Manager to install the Service Pack from the Sage website, and it would appear that that has cured the problem...I hope!

John