What do I need to consider when upgrading Sage 50?
As new versions of Sage 50 come out, we endeavour to keep Weighsoft fully compatible. Below are a few things to consider when upgrading Sage 50:
All instances of Sage need to be upgraded to the same version.
Sage 50 can be installed on multiple computers, all of which are reading the same financial data. When upgrading Sage 50 it is very important to ensure that ALL instances of the program are upgraded to the same version. e.g. All the PCs in the office that are running Sage, as well as the installation of Sage on the Weighsoft server (and any other servers that may be running it) all need to be upgraded. If any instances are not upgraded to the correct version, they won't be able to log into the system.
Is your version of Weighsoft compatible with the version of Sage 50 to which you are upgrading?
If your version of Weighsoft is not compatible with the version of Sage to which you're moving, a Weighsoft upgrade will be required first. Consult the table below to see if your version is compatible. (You can find your version of Weighsoft by going into Administration and then clicking on About).
Sage 50 Version | Weighsoft Version |
v30 | 5.514 |
v31 | 5.524 |
v32 | 5.529 |
Note: Sage 50 has the option to install a 32-bit or 64-bit version of the application.
If your version of Weighsoft is below 5.531 then you must install the 32-bit version of Sage 50 in order to still use Direct Posting. If you use the 64-bit version of Sage you will need to use Flat File posting instead.
If your version of Weighsoft 5.531 or higher or higher you must install the 64-bit version of Sage 50 in order to still use Direct Posting.
Is this a full Sage upgrade or a patch?
A full upgrade would be if you're moving a full version or more (e.g. from v28 to v29). This kind of upgrade means that once the Sage installations have been upgraded, support will need to connect to your server and make changes in the background to update and reinstate the link between the two systems.
If you are carrying out a full upgrade, please raise a case with support beforehand and reference the title of this article. This allows us to be prepared to make the changes and minimize any downtime you might experience.
A Patch upgrade would be moving from, for example, v29.1 to v29.2.
A Patch upgrade does not usually require any additional work to be carried out by support afterwards, although a server reboot may still be required when the update is complete.