We have received the following advance announcement from Sage Software regarding the release of the 2020 edition of Sage 50. This is the first notice we have received that there is in fact a 2020 edition in the works, and …
Sage Software has recently posted a security bulletin regarding a potential “folder permissions” problem for users of Sage 50 2016 and earlier. This announcement has come on the heels of the release of Sage 50 2018.2, which is designed to address …
Sage Software has recently notified us of a change in the “Sage 50 obsolescence policy” for supporting editions of the Sage 50 product prior to the current edition. As of February 28, 2018, Sage will end support for any edition …
The latest update to Windows 10 appears to have “broken” some key elements of Sage 50 2018 and 2017, generating a “Sage 50 has stopped working” error, which then closes the Sage 50 application. Sage Technical Support reports that the …
Sage Software has recently released a service release (2016.2) for the Sage 50 product line (all editions). Users logging out of Sage 50 will likely see an announcement that a new update is available, and should be installed on the …
Sage 50’s Latest Service Release – Proceed Carefully Read more »
The notice reprinted below from Sage Software has been recently posted in the “What’s New” section of the latest Sage 50 product release. This notice may – or may not – be sent to all current subscribers, so I thought …
The Sage “re-branding” initiative is not going away – Peachtree will still become Sage 50 U.S. Edition effective this May – but the transition to a “subscription only” sales model has apparently been shelved for this year. The reseller webinar …
As most customers have heard by now, when Sage releases the next version of Peachtree in May, the product will be officially re-branded, from “Peachtree” to “Sage 50 – U.S. Edition”. What has not yet been widely publicized, however, is …
We may have stumbled upon a solution to a really obscure Peachtree problem that has plagued more than one of our clients. Thanks – and kudos – to Anthony Licate of Spidernet Technical Consulting for working through this one and …
In one of the shortest lived posts we have ever made, we need to now retract our earlier statement about the Peachtree 2010 link with Timeslips being “non-functional.” Don’t know why it would not work yesterday, and don’t know why …