Sage 200 2016 SP2

Sage 200 2016 SP2 has been out for a while now. One key issue that impacted users in Sage 200 2016 were the restrictions on Accounts which were placed ‘On Hold’. There is an issue with entering Memo’s and also it is not possible to allocate transactions. SP2 fixed the Memo issue. It didn’t fix

Sage 200 Extra 2015 – SERVICE PACK 3 Released

Service pack 3 has now been released for Sage 200 Extra 2015. There are a number fixes included as detailed in Sage 200 Extra 2015 SP3 Issues Fixed . Sage 200 Manufacturing Stock Projection Details Some changes have been made to improve compatibility with Windows 8, Windows 8.1 and Windows Server 2012, these changes also make a consistent look

Sage 200 Extra 2015 – SERVICE PACK 2 Released

Yesterday finally saw the release of the much-anticipated Service Pack 2 for Sage 200 Extra 2015. One of the key items as part of this is the support of Windows 10 operating system. There are lots of fixes and some additions as detailed in this document released with the update – Reports There are some New

Sage 200 and Windows 10

Short, important post! Microsoft have now released Windows 10. Please be aware that this is NOT supported for any current versions of the Sage 200 suite. All being well Service Pack 2 for Sage 200 Extra 2015 will include Windows 10 compatibility. This is currently scheduled for 30th September 2015.  

Sage 200 2015 – SERVICE PACK 1 Released

Sage 200 2015 Service Pack 1 is now available. Business Partners should note the different method of installation on Clients. This service pack contains two files: Sage200v2015SP1ClientPrerequisites.exe Sage200v2015SP1.msp On a client PC both files must be run, in that order, to ensure the service pack installs correctly. Sage200v2015SP1ClientPrerequisites.exe checks the client files and ensures that

Known Issue 5924: Details of Held Journals are lost

There is a Known issue (5924) which is fixed in Service Pack 1 for Sage 200 2013 R2 where the details of held journals, which were created from Journal Templates, are lost if more than one journal has been held. NB. there was a hotfix for this originally but this is now rolled up into

Service Packs released for 2011and 2013

Following on from my Early Settlement Discount post, Sage have now released the Service Packs for Sage 200 2011 and 2013 (NOT 2013 R2). As suggested previously these only serve to be a temporary solution to the legislation change for Early Settlement Discounts and will still require you to process manual transactions in order to correct your

Early Settlement Discount Legislation Changes for Sage 200

On 01 April 2015, the legislation when raising or receiving a VAT invoice including early settlement discount will change. The change affects you as a supplier who offers early settlement, and/or as a customer who receives early settlement discount, where an invoice is issued. For the current legislation, up to 31 March 2015, suppliers who offer early settlement

Sage 200 2013 Insatllation – A share NOT called Sage!

In a recent installation of Sage 200 2013 (RELEASE VERSION) I found that the server already had a shared directory called ‘Sage’. This was being used for Line 100 data purposes. In an attempt to avoid issues with Line 100 (which is their current Live system) and current ODBC reports, I decided the best approach was to

Service Pack 5 for Sage 200 2011 – RELEASED!!!!

Service pack 5 for Sage 200​ 2011 has today been released. This is the last “planned” service pack release for Sage 200 2011, although hotfixes will continue to be released as required. The next main release for Sage 200 will be Sage 200 2013, which will be for both Cloud and On Premise versions. Service