Determine the Type of System

The main Changes of custo diagnostic 4.6 are:

• does not Support MDB Databases anymore
• does not Support distributed Databases (eg. ConfigDB local, PatientDB centralized) anymore
• does now support Config DB in not Latin1 Language based Operating Systems
• Database is no longer backward compatible to older Versions of custo diagnostic

Therefore, it is necessary to prepare your running system in a way that it can be updated sucessful.

To apply the right Update Strategy you have to determine the Type of the running System. Here some Samples of Systems:

• Local System MDB: System with one localized Database, eg. Stand-alone Workstation
• Local System SQL: System with one localized Database, eg. Stand-alone Workstation
• Central System MDB: System with centralized Config Database and Patient Database, eg. Network Workstation with Databases located on a Server
• Central System SQL: System with one centralized Database (ConfigDB and PatientDB are located in one SQL Database), eg. Network Workstation with Database located on a Server
• Satellite System MDB: with access to a centralized and localized Database (below custo diagnostic 4.4.4)
• Satellite System SQL: with access to a centralized and localized Database
• MDB compatible Central System: System with several distributed Databases, for Example one localized Config (MDB or SQL) Database and one centralized Patient (MDB or SQL) Database
• Pseudo Tenant System: for Example one centralized Database (Config + Patient) and several distributed centralized Patient Databases for several Users

Preparations

For the Systems 'Local System', 'Central System', 'Satellite System' we recommend:

• update the whole Installation to custo diagnostic 4.5.5. If your Original Installation older than Version 4.5.x you can use your Universal License Dongle to startup the updatet Installation (if the customer dont bought an Update to custo diagnostic 4.5.x).
• convert every MDB Database to an SQL Database. This can help to recognize some Data Problems inside the MDB Database.
• make the System running again
• make a Backup of the Database (local Database of the Satellite System are excluded - its better wo empty the Database and recreate it afterwards)

For 'MDB compatible Central Systems' we recommend:

• update the whole Installation to custo diagnostic 4.5.5. If your Original Installation older than Version 4.5.x you can use your Universal License Dongle to startup the updatet Installation (if the customer dont bought an Update to custo diagnostic 4.5.x).
• convert the whole System to an 'Central System SQL'
• make the System running again

For 'Pseudo Tenant Systems' we recommend:

Update a Local System MDB

A direct Update of an 'Local System MDB' to custo diagnostic 4.6 is not supported. We recommend to convert your System to a running 'Local System SQL' first and continue with 'Update a Local System SQL'.

Other Way: Import MDB Database: .. to do ..

Update a Local System SQL

• Shutdown custo diagnostic
• Update the License on the local CodeMeter
• Install custo diagnostic 4.6 as an Update
• if you Start custo diagnostic (custo manager.exe) maybe you will get this Message:
  
  
  • Click on 'Confirm' to close this Messagebox
    
    
• open the custo Service Center and confirm the 'Invalid database settings' Message again
• expand the Menu 'Database' and Click to 'Support Configuration'
  
  
  
• Click on 'Clearup all MDB settings' in the Area 'Tools' to remove all old existing Database Settings in the ConfigDB
• after you get
  
  you can close the custo Service Center
  
  
• Start custo diagnostic (custo manager.exe) again
• when custo diagnostic ist starting the Database will be updatet to a newer Version
  
  You have to click on 'Update' to make the Update. If you are unsure you can click on 'Quit program' to terminate the process unsucsessful.
  
  
• after the Update has been done (takes some seconds) custo diagnostic will start and is ready to use
  
  

Update a Central System MDB

A direct Update of an 'Central System MDB' to custo diagnostic 4.6 is not supported. Please convert your System to a running 'Central System SQL' first.

Update a Central System SQL