The "Database Mismatch" error in the Vitals system occurs when the database on the handheld controller (TC-100 or HC-100) does not match the database currently open in Vitals Desktop. This mismatch can happen if:
- The controller was synced with a different database previously.
- The structure or content of the database has changed (e.g., fields added or removed).
- The controller is being used with a new or different PC.
What the Error Means
When Vitals Desktop detects that the database on the controller is different from the one currently open, it prompts you with options to ensure data integrity and prevent overwriting or losing data.
Options You’ll See and When to Use Them
1. Import Activities (normally use this)
- Use this if: The Vitals Desktop database is the correct one and you only want to import new activity data from the controller.
- What it does: Imports activity records without changing the valve database structure. Updates only the valves that have been modified.
2. Import Activities + All Valves (only use if main database on PC is lost)
- Use this if: The Vitals Desktop database is empty or missing valves, and you want to import both activities and all valve records from the controller. Typically used when the main database in PC or Vitals Desktop has been lost and the controller data will be used to back-up the lost valves.
- What it does: Adds all valves and activities from the controller to the desktop database.
Best Practices
- Always back up your database before importing. (especially if last data transfer was done a few months ago).
- If you're unsure which database is correct, check the valve and activity counts on both the controller and desktop.
Avoid frequent switching between databases unless necessary.