Mixing usage of Panorama X 10.2 (or newer) with Panorama X 10.1 (or earlier) can be problematic. For example, suppose you follow these steps:

After following these steps you will no longer be able to open the Mailing List database with Panorama X 10.2 (or later). When you do, you’ll see an alert saying that the database cannot open because it is damaged.

Fortunately the database isn’t actually damaged, so this problem is easily resolved. To open the database, open the Panorama>Preferences window, switched to the Advanced panel, and un-check the Database Integrity Checks option.

Once this option is disabled, you should be able to open the “Mailing List” file. Once you have saved the database the problem is fixed, and you can re-enable the integrity checking preference. As long as you never open the file again in Panorama X 10.1 (or earlier), the problem will not occur again.

Why can’t 10.1 and 10.2 be mixed?

When Panorama X 10.2 saves the database to disk, it calculates a checksum for the database. This is like a seal that validates the contents of the file. When you later open the database, Panorama X 10.2 checks to make sure that the file matches the checksum seal. If it doesn’t match, Panorama refuses to open the file and tells you that it is damaged. For example, this could happen if there is a hardware problem with your storage medium (disk drive).

Since it was written years ago, Panorama X 10.1 doesn’t know anything about the checksum that has been saved with the file. When you modify and save the database, the checksum isn’t updated. That’s fine if you only use 10.1. But when you open the database with 10.2 again, it sees the incorrect checksum and refuses to open the file.

You may wonder why this problem doesn’t occur the first time you open a database with 10.2. That’s not a problem because there’s no checksum. Panorama X 10.2 understands that a completely missing checksum doesn’t mean the file is damaged, it simply means that this is an older database that has never been used with Panorama X 10.2 before.

The best solution to this problem is to completely upgrade to 10.2. If you have multiple computers, upgrade all of them at once. (Another solution would be to permanently disable the Database Integrity Checks option on all of your computers running 10.2, but we don’t recommend that.)

To learn more about this topic see Database Integrity Checks.

See Also


10.2NewNew in this version.