Process for Upgrading from earlier versions of Idealpos

Below is best practice for upgrading Idealpos from 4.0 to the current version.
A note before continuing: a direct upgrade can be tested offline first (for example, 6.03 Build 181 to 7.1 Build 18 or v8 Build 2) as this can sometimes work. If this fails, the steps below can then be used.

Important Notes:

  • Backup the database between each upgrade step, so you can go back if required.
  • Test thoroughly offsite before performing on a live site
  • Where possible, ensure there are no live Bar Tabs or Tables before converting.  (If the conversion must be done with data on Bar Tabs and Tables, do a report first, so items can be re-added manually after the conversion if required).
  • All terminals must be upgraded at the same time, as there may be database structure changes between the two versions that can cause corruption and other issues.
    6.03 Framework Patch is required for all 6.03 builds

Version steps when converting:

  • 4.0/5.0 to 5.5 Build 91: Backup the IPS.mdb file from 4.0/5.0. Do a Full System Reset in 5.5 Build 91. Copy the IPS.mdb file into the 5.5 folder, overwriting the file of the same name. Start 5.5, and the conversion is triggered.
  • 5.5 B91 to 6.01 B23 (builds from versions 6.01 or 6.02 will require 6.0 Framework and then the 6.01 Framework to be installed first)
  • 6.01 B23 to 6.03 B80 (builds for version 6.03 will require 6.03 Framework installed)
  • 6.03 B80 to 6.03 B159 (B159 is here: https://drive.google.com/file/d/1AXUVvl4Qu1FQmlEXlJ46nMypXWsxi5rN/view?usp=sharing )
  • 6.03 B159 to 6.03 latest build
  • Uninstall Idealpos 6.03 from Control Panel > Programs
  • Install original 7.0 Framework (from 2015). If the following message displays:
    "You must be running on Version 6.03.0132 or above before Upgrading to Version 7 (Start up POS on Version 6 Build 132 or above and then uninstall version 6 prior to installing version 7)"


    Download the attached FrameworkRegistry181.zzz file, rename as .reg, double-click and accept adding it to the registry, and then run the Framework installer again.
  • 6.03 latest build to 7.0 Build 27 (version 7.0 builds up to and including build 27 will need original Version 7 Framework (2015) installed).
  • Install Framework-2017 or the Framework-2017 patch
  • 7.0 Build 27 to 7.0 Build 57
  • 7.0 Build 57 to 7.1 latest build.
  • Install Idealpos 8 Framework
  • Install the latest build of Idealpos 8/9.

Note:

  1. Before installing 7.1 Build 14 or greater, install the Idealpos7-FrameworkPatch-2020.exe. If the Build is accidentally installed first, just install the 2020 Framework Patch, and then install the Build again.
  2. Idealpos 7.1 Build 7 and onwards requires .NET Framework 4.6.1. Therefore, Build 7 and onwards cannot be installed on Windows Vista and Windows Server 2008 as the highest version of .NET Framework supported by these Operating Systems is .NET Framework 4.6. This can be downloaded from https://docs.microsoft.com/en-us/dotnet/framework/deployment/deployment-guide-for-developers?redirectedfrom=MSDN
  3. Information regarding the .NET Framework System Requirements can be found https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements



Procedure for each version step:

  1. Restore database (or.MDB file)
  2. Start POS to allow conversions to occur (wait at least 10 minutes. There is no visual message, but normally there is a wait icon while conversions are run).
  3. Close and start POS again to ensure conversion complete (sometimes it does not appear to complete conversion on first start-up.)
  4. Do a Void All transaction and check audit numbers
  5. Check Customer trial balance, note for future reference to compare after each upgrade step.
  6. Check that the POS screens look the same
  7. Check the number of customers
  8. Check the number stock items and do a couple of stock item spot checks.
  9. Check Table Maps
  10. Validate (in IPSUtils)*
  11. Compact/Repair (in IPSUtils)
  12. Validate (in IPSUtils)*
  13. Backup
  14. Continue to the next version step and repeat the procedure.

Note: If a 3709 error occurs after upgrading, this could mean that a step was skipped in the update process (for example, the installing and running of Build 57).

*If errors are found while validating the Access database, refer to this Solution: Recover the Access Database.

6.03 Framework : https://drive.google.com/file/d/1TTv6WvxBKNujNEYgg3twYM52T6LmKNhw/view?usp=sharing 
6.03 Build 159: https://drive.google.com/file/d/1AXUVvl4Qu1FQmlEXlJ46nMypXWsxi5rN/view?usp=sharing
6.03 Build 181: https://drive.google.com/file/d/1IRukGf46O6G2Im7yxDM-FAmGxY96FPhc/view?usp=sharing
Framework 2015: https://drive.google.com/file/d/1vCogQ-F3MzVST-vALatm6mJmqadIe1TE/view?usp=drive_link 
7.0 Build 27: https://drive.google.com/file/d/18YtQtpV7-D5UQSxcmdkIa56GlSrrEnSC/view?usp=sharing
Framework 2017 Patch: https://drive.google.com/file/d/108iZopDHah90EsrVFlCrU8K8ZjgNnRg2/view?usp=sharing
Framework 2017: https://drive.google.com/file/d/1TTGN61tpk6Et5cppy3gnePNhU4ym8aoS/view?usp=drive_link
FrameworkPatch-2020-2: https://drive.google.com/file/d/1T7K5lYWKSsOoZGBNpXRvnKql9QtfuCtl/view?usp=sharing
7.0 Build 57: https://drive.google.com/file/d/1gQ9bNdRNXlCQfQ2cvug4cdXdG4wDLgK7/view?usp=sharing
v8 Framework: https://drive.google.com/file/d/1oi4GRiSp4JQArV8E40SX0CqKoHeXpzvV/view?usp=drive_link

FrameworkRegistry181.zzz