03-23-2018, 10:34 AM
Hi Johan,
I definitely don't like the sound of that at all. The newest update definitely shouldn't have caused problems like that. It sounds to me like your database didn't update to the latest version. I have a test build I can send to you that will probably get past those update errors allowing you to use 2.1.2. Shoot me an email at mike@zubersoft.com if you want to test that so I can send you a link. If you want to manually check the database, look at the user_version and let me know what it says. 43 is the latest version - if it's below that, then that is definitely the problem. You would be the third user I've spoken to who has encountered this, so I may need to put out an update. It does mean that there could potentially be issues in your database though, as not being able to update the database is always a bad sign. Those issues would be mainly with annotations. The latest update just exposes this problem more severely as I changed a data structure that every song utilizes when loaded, so it causes a crash if the database doesn't have the correct tables in place.
I don't think anything has changed in v2.1.2 in regards to disk/file access. What was the last version you were using? I changed the backup/restore dialogs awhile ago to give users the choice to pick the source/destination without having to do it in the file browser itself.
Mike
I definitely don't like the sound of that at all. The newest update definitely shouldn't have caused problems like that. It sounds to me like your database didn't update to the latest version. I have a test build I can send to you that will probably get past those update errors allowing you to use 2.1.2. Shoot me an email at mike@zubersoft.com if you want to test that so I can send you a link. If you want to manually check the database, look at the user_version and let me know what it says. 43 is the latest version - if it's below that, then that is definitely the problem. You would be the third user I've spoken to who has encountered this, so I may need to put out an update. It does mean that there could potentially be issues in your database though, as not being able to update the database is always a bad sign. Those issues would be mainly with annotations. The latest update just exposes this problem more severely as I changed a data structure that every song utilizes when loaded, so it causes a crash if the database doesn't have the correct tables in place.
I don't think anything has changed in v2.1.2 in regards to disk/file access. What was the last version you were using? I changed the backup/restore dialogs awhile ago to give users the choice to pick the source/destination without having to do it in the file browser itself.
Mike