WonderPen User Manual

Appearance

Database Version Incompatible ​

If you see a Database version incompatible message (or similar) when starting WonderPen or opening a library, it usually means the database has already been upgraded by a newer version of WonderPen, and the older version you're currently using can no longer open it.

Why does this happen? ​

WonderPen uses databases to store documents, settings, and other data. Sometimes a new feature needs to store additional information, which requires a change to the database format. For example, adding a new document property may require an extra field in a database table—much like adding a column to a spreadsheet to hold that information.

When an update requires this kind of change, the newer version of WonderPen upgrades the database to the new format. Older versions only understand the original format and cannot correctly handle the upgraded data, so they show a “Database version incompatible” message. This usually does not mean the data is damaged; it means you need a version of the app that understands the new format.

Not every app update changes the database format. Only updates involving these format changes may prevent older versions from opening the database.

This message can appear for the following databases:

  • The configuration database
  • The user database
  • The library database

Resolution ​

Update WonderPen to the latest version, then open the library again. Don't keep retrying with the older version, as that may make WonderPen mistake the library for a corrupted one.

If you use the same Cloud Library across multiple devices, or sync the same Local Library, try to keep all those devices on the same or a newer version of WonderPen. Once one device upgrades and opens the library, other devices on older versions may no longer be able to open it until they are upgraded to a compatible version.

WARNING

Don't manually edit the database files inside a library, and don't overwrite an upgraded library with an older version. If you need to roll back, back up the current library first, then contact support or restore from a backup.