Did you create the database in Panorama X 10.2b17, then later open it in 10.1 and modify it, then open it in 10.2b17 again? I’m thinking you worked with this database on your computer with the beta version, sent it to a client that doesn’t have the beta, then they sent it back and you encountered the problem. This is actually a feature!
If you want a database to be usable in older versions of Panorama X, you’ll need to disable the Save database with integrity seal option (in the General panel of Database Options) for that database.
You can recover from this situation without resorting to a text file. Instead, you can temporarily disable data integrity checks using the Advanced panel in the Preferences window.
I hadn’t thought of this situation of taking a database back to a previous version of Panorama. I’ve just now added a note about this in the documentation.
By the way, most of you do not have b17 yet, so you don’t need to worry about this for the moment, but you will get a new beta version soon.