KMyMoney 5.2 and SQLITE-Database from 5.1.3

Hi KMyMoney Team,

Is it correct that I can’t transfer an SQLite database created with 5.1.3, whether with or without a password, to 5.2?
So, it’s true that with 5.1.3, I first have to create a .kmy file, open it with 5.2, and then export it as a new database.

Or is something possible with version 5.2.1?

Regards,
Udo

Apparently fixed in 5.2.1

is there a release date for 5.2.1 yet?

Question: could this be the reason KMM is not able to open my sqlite db file anymore? I last opened it over a month ago, June 11 to be exact. I’m on an arch based distro, so there could have been updates since then to KMM. Yesterday I launched KMM and instead of loading the overview page it just goes unresponsive and hangs until I close it. I thought my file had gotten corrupted somehow but I can see all the data inside sqlite browser just fine.

Does the fix in 5.2.1 help my situation?

drewmama: while it seems likely, to know for certain whether your problem is the same as the one fixed in 5.2.1 (no release date yet, but soon) we need more information. If you launch KMM from command line, you should see some error message about what the problem is. Also, with problems such as this please let us know the exact version of the program - you can run “kmymoney -v” to find out. That would confirm you did get upgraded from 5.1.3 to 5.2.0.

Thanks ostroffjh. kmymoney -v returns 5.2.0 so I got the upgrade. I did some more troubleshooting and here’s what I found:

My db file is an encrypted SQLite file. When I try opening the db through the terminal, KMM launches and then this error shows up:


I click OK and control is handed back to KMM. No file was loaded.

If I then try to open the same file from the recents list, I get a window to enter the file password. Enter my password and click ok and KMM hangs until I close the window.

In case you start KMyMoney from the command line, you should see an infinite loop showing the following two messages:

Perform upgrade to db layout version 14
Unknown version number in database - 13

which causes the application to remain unresponding.

That one will be fixed with 5.2.1.

That is exactly what I see. Will wait for 5.2.1 then. Thanks for all the help here.

Drew