Before upgrading it is important to check what the enhancements and fixes are in order to determine whether additional setups and user training will be required after the upgrade.
NB. Always test the upgrade on a copy of the live DB before commencing the live upgrade.
Get all the users to log out and delete the QuickEasy.exe to make sure nobody can login while you are upgrading.
Backup the live database.
Rename the live database - eg. Database_date.FDB - so that you don't delete the live DB when you restore the backup.
Restore the Backup without checking the 'Replace' flag - that ensures your backup is working correctly and you can't erase the live DB (which you renamed).
Open Tools.exe and download the upgraded QuickEasy.exe.
Use Tools.exe to execute the Upgrade Script. NB If it's a major upgrade (eg. from Ver 2018 to Ver 2019), you need to first run the last Fix script for the current version before executing the Upgrade Script for the current version.
Use Tools.exe to execute the last Fix script for the new version.
Decompress and restore the new QuickEasy.exe to the QuickEasy folder.
Test that the upgraded version is working correctly.
Contact Helpdesk to schedule an appointment for a consultant to demonstrate the new version onsite or remotely using Teamviewer.
If, after the demonstration, you feel that upgrading will benefit your business, your consultant will prepare a quotation and schedule the upgrade.
A few days before the scheduled upgrade, our Helpdesk will obtain a copy of your database and run a test upgrade on it.
The upgraded copy of the database will be installed at your company for training users to ensure they are familiar with the new functionality before upgrading the live database. Every user should test the functionality they use on the new version, paying attention to new template layouts, upgraded reports, etc.
When all the users are comfortable with the new version, your consultant will upgrade the live database.
Run the old and upgraded versions next to each other and compare the following.
Ledger - Remove all the filters to view all the transactions and compare the Total, Allocated and Unallocated fields.
Customer Age Analysis - Compare at current date as well as at a prior date.
Supplier Age Analysis - Compare at current date as well as at a prior date.
Trial Balance - Compare at current date as well as at a prior date in the previous financial year. Compare a full year as well as a few months in the year.
Income Statement - Compare current period as well as a prior period.
Balance Sheet - Compare current date as well as a prior date.
Compare total stock levels at current date for all Categories in the BOSPrint: Materials module.
Open all the core non-accounting transaction types (Quote, Sales Order, Work Order, Purchase Order).
Remove the data filters to view all the transactions and compare the transaction count and totals.
Establish which reports are in use (in later versions, QuickEasy creates an Audit when a report is executed) and compare the old and upgraded report values.
If any discrepancies are found, investigate the cause of the problem so a solution can be found BEFORE upgrading the live database. This should be done before the upgraded demo is installed at the customer.
Make sure that each QuickEasy user tests the functionality they use in the upgraded demo and let them sign off on it. This is also a way to establish the actual user-count in the company.
If you are upgrading the same version of BOSPrint, you may be required to run the fix script. You can find it in the Fixes folder of the downloadable scripts folder.
The concept with the fix scripts in BOSPrint is that you only have one fix script for each numbered version, which can be executed multiple times. So every time you do a same-version upgrade (exe Upgrade), you simply run the Fix script for that version.
The Fix script only updates Triggers and Procedures, so it executes in a few seconds and can be run while users are logged into QuickEasy.
The Fixes are also updated to the main scripts, so when upgrading from an earlier version, you never need to execute the Fix scripts.