I am having an issue with Sage 2013, client manager version.
When I try to post a recurring entry, the software shuts down. On reopening and running the error check, it does seem to have posted the journal. I wondered if any of the Sage Gurus on here have experienced this, and know of anything that might be causing it?
I have also had issues with the program closing itself down when I try to double click into nominal ledgers, and Sage Support have had me doing a reindex and compression on the NL's but it doesn't seem to stop it from happening again.
I am wondering if these issues are created because of a global problem, linked to something within the prgram files/data?
The first problem, it shutting when posting a recurring transaction, is a totally new one on me.
The second one, however... when you say it happens when you try to double click into nominal ledgers, isn't quite the same, but I have experienced it unceremoniously quitting when clicking on the "Details" tab of nominal, sales and purchase ledger accounts. I suspect it's probably the same bug*.
Sage have known about it for at least as long as I have, because I made sure they knew about it the first time it happened to me - but they seemed to be quite clueless as to the cause, so whether that's changed (and whether it's therefore fixed in the 2014 version) I don't know (because I no longer pay the Sage tax after an argument with them about spam).
* It really is quite a nasty little beggar if it's the same bug. The reason I say it "unceremoniously" quits is because that is *precisely* what it does. The user gets no warning; just click on the tab and Sage vanishes - even if you have (say) a window open with a load of transactions you've keyed in but haven't yet saved (you might be looking in the detail of a particular account to check where you've previously posted something unusual, for example, before adding the latest recurrence of the same to the transactions you've keyed in so far).
Sage's suggestion is that you can get around it by highlighting the account in question, and click on the "Activity" toolbar button, instead of double clicking the account to open the full record and click on the "Details" tab - and that may be very marginally quicker based on the physical actions, but when you factor in thinking about doing that? No, it isn't.
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
"Vince's software specific reply obviously takes precedence over this one but just putting out the idea that the issue maybe physical rather than software specific."
IIRC I investigated the memory and processor load possibilities around the time I reported it to Sage, and found nothing to indicate that was the problem - at least nothing that could be fixed by increasing the memory available to the software.
What that doesn't rule out, though, is something more internal to Sage; a buffer overrun and a screwed up bit of bounds checking, perhaps - but that's not something I can check, and I suspect that would be more likely to result in corrupted data than an unexpected quit. (Though an unexpected quit would be far, far preferable!)
-- Edited by VinceH on Sunday 10th of November 2013 04:35:32 PM
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
Thanks for the tip about using the tab bar "activity" button instead. I will try and get into the habit of using it, as, like you say, it literally just quits out without warning, and not all the time.
The same thing is happening with the recurring entries. No warning, just disappears.
I have never seen these issues before, and I was using Client Manager in my old firm, so I suspect its related to 2013 then?
The advice from Sage with the NL problem was to reindex and compress nominal ledgers. This fixed the issue temporarily, as it has happened since. I have run this function again, in the hope it would fix the recurring entries issues - reindexed and compressed the NL and bank - and it appears to have worked, as I just posted a recurring entry without it closing down
just out of interest, start task manager before doing it next time and see what happens to CPU and Memory.
Just a left field suggestion but see whether the action is very memory or processor intensive.
Some programs will shut down if they get a memory overflow, others can handle it internally.
If the issue is down to memory then increasing physically memory, upping the swap file size (hard drive memory) or reducing other thing that your computer is doing at the same time may fix the issue.
If its its processor issues where the machine cannot actually handle the software then thats somewhat more expensive to fix.
Vince's software specific reply obviously takes precedence over this one but just putting out the idea that the issue maybe physical rather than software specific.
kind regards,
Shaun.
__________________
Shaun
Responses are not meant as a substitute for professional advice. Answers are intended as outline only the advice of a qualified professional with access to all relevant information should be sought before acting on any response given.
"The same thing is happening with the recurring entries. No warning, just disappears."
Although it's a different context, that it's exactly the same behaviour suggests to me it could very well be another manifestation of the same bug - which is worrying, because if that's the case, then where else is it likely to crop up?
"I have never seen these issues before, and I was using Client Manager in my old firm, so I suspect its related to 2013 then?"
It seems to have appeared (for me) with the 2013 edition. As I said, though, whether it's fixed in the subsequent release is anyone's guess. With a bit of luck, although they expressed bafflement when I first brought it to their attention, that was some time ago - so perhaps they've been able to track it down and fix it by now, and the fix is in the 2014 edition, or will be in the 2015 edition.
Perhaps.
(And if so, given the price of the software, IMO Sage should have a duty of care to supply a patch to users of affected versions. I can't see them doing that, though!)
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
Create a new user in Sage 50 and then try making it crash as the new user.
You might be able to fix this by deleting your user files in the accdata directory, but it might be easier/safer to just use a different user name
2:the recurring entries table may be corrupted and is not being checked/fixed by the routines.
I would...
BACKUP
Delete all the recurring entries
Delete the files in ACCDATA called RECUR.DTA and RECURING_INDEX.DTA
Reindex and compress
Go back add a recurring entry and see if it breaks still.
If it still breaks, I was wrong restore your backup and you have lost nothing.
If I am right, then re-entering the recurring entries could fix it.
__________________
For just about anything Sage :- switch to renting, pay-as-you-go sage support, sagecover, upgrades, application integration, reports, layouts, analysis or any other help making life with sage easier/less time consuming Contact me.
PS When you reindex and compress, there is an option that alters how the reindexing and compression is done.
Changing this sometimes fixes things
You need to open the Sage.ini file in youe windows directory and find/add/alter the line in the [SG50] Section
CompressUsingFileSize=1 is non=standard method
CompressUsingFileSize=0 (or no entry at all is the normal method)
__________________
For just about anything Sage :- switch to renting, pay-as-you-go sage support, sagecover, upgrades, application integration, reports, layouts, analysis or any other help making life with sage easier/less time consuming Contact me.
