x Want to participate? Join the group to interact
Options
  • Replies 8 replies
  • Subscribers 56 subscribers
  • Views 3420 views
  • Users 0 members are here
Browse Forums
Announcements
764
topics
17
replies
Financial year end
78
topics
178
replies
General Discussion UK
7k
topics
19k
replies
General Discussion Ireland
176
topics
312
replies
Install your software
139
topics
378
replies
Making Tax Digital
286
topics
692
replies
Manage your VAT
151
topics
324
replies
Protect and repair your data
45
topics
138
replies
Run your accounts remotely
86
topics
198
replies
Working with the bank
116
topics
294
replies
Stuart Mohamed

Sage crashes after editing or deleting a transaction when in the Supplier or Customer Activity screen.

Posted By

Hi all,

My issue is pretty much as described in the title and I just wondered if others are having this issue as well.

So to be clear as an example, let's say I have posted a customer receipt but I have mistakenly posted it using the wrong date. I notice the error while viewing the transactions in the customer activity screen. At the top of the screen there are options to either view, edit or delete the transaction. So let's say I highlight the transaction in question, hit on edit, change the date then hit save. At this point, although Sage does make the edit, it then just crashes and my session ends forcing me into restarting the program and having to run the check for errors function - all very time consuming and annoying. 

It's been like this for quite a while now. When I first experienced it, I just figured it was a new feature and perhaps a bit buggy and that it would probably get rectified in a future update. However it's been too long now and I just wanted to understand if it was just me or if others are experiencing this too.

Thank you

Stuart

Parents

  • Just as an update to this, my original post did have an error in it. I gave an a example of the issue and described the situation when I was in the customer activity screen. Well that was wrong, it doesn't happen in the Customer activity screen,BUT it does occur when in the Bank activity screen. In other words, if you make an edit to a payment or a receipt etc whilst in the bank activity screen, although Sage does make the edit, it crashes the system immediately after, and when you log back in, it prompts you to use the check data option as it 'detected Sage wasn't shut down properly' or words to that effect. I'm not sure this makes any difference but thought I would share anyway.

Reply

  • Just as an update to this, my original post did have an error in it. I gave an a example of the issue and described the situation when I was in the customer activity screen. Well that was wrong, it doesn't happen in the Customer activity screen,BUT it does occur when in the Bank activity screen. In other words, if you make an edit to a payment or a receipt etc whilst in the bank activity screen, although Sage does make the edit, it crashes the system immediately after, and when you log back in, it prompts you to use the check data option as it 'detected Sage wasn't shut down properly' or words to that effect. I'm not sure this makes any difference but thought I would share anyway.

Children
  • in reply to Stuart Mohamed

    Hi Stuart.

    Thanks for using Sage City.

    What i would do if this happens again there maybe issues, reading a certain file in the background of Sage, We usually would then advise to follow the steps below. 

    1. Click File, then click Maintenance and click Check Data.
    2. Click the Warnings tab and if either of the following warnings appear, make a note of the amounts:
      • Sales aged balance disagrees with Debtors Control by (amount).
      • Purchase aged balance disagrees with Creditors Control by (amount).
    3. Click the Technical Information tab then from the Dataset Information section, note the number of Splits.
    4. Click Recovery Tools, when prompted, follow the instructions and create a data backup.
    5. Click Reindex and Compress All, then click OK.
    6. Click Recalculate Transaction History, then click OK.
    7. Click Recalculate Period Values, then click OK and click Close.
    8. When prompted to check the data again, click Yes.

      If the error is still present, you must restore an error free backup and reprocess, otherwise continue.
    9. Click the Warnings tab and check for aged balance warnings:

      If the warnings disappear, continue to the next step.

      If the amounts differ to step 2, restore an error free backup and re-process, otherwise continue.
    10. Click the Technical Information tab then in Dataset Information, check the number of Splits.

      If the number differs to that in step 3, restore an error free backup and re-process.

    Hopefully once this is done it should stop any issues with your data/program misbehaving or point us to the main source of the problem.

    If this has answered your question please click More > Verify Answer.

    Regards,

    Michael
    Sage UKI

  • in reply to Michael Goossens

    Hi Michael,

    thank you for the feedback. The issue only happens when I edit in the Bank activity screen which is very seldom.

    I have run the checks you said about before whilst tackling a different issue and if I remember correctly, those checks took well over an hour to run. So on balance at best I think I'll have to train myself to not edit in that particular screen and at worst, learn to live with it.

    Thanks again

*Community Hub is the new name for Sage City