I cannot open my database in 1.3.1 version !

[Feanx]

Hi !
I've upgraded to 1.3.1 version.
I have 2 databases.
One is OK
The other cannot be opened with the log file I join here :

log.txt

(4.36 KiB) Downloaded 410 times

I have 2 computers with 1.3.1 running, with se same result  : so this database is not compatible with 1.3.1.
I have downgraded to 1.2.7 and everything is OK, the database is opened and MMEx works well...
What is wrong with this db ? (sorry I cannot share the db)

PS : Multiple instances are no longer supported in 1.3.1 !!! I cannot work with 2 databases if I cannot open both at the same time !
I downgrade my both computers to 1.2.7 until everything is fine !

[apeman]

Exactly the same thing has happened to me. When I try to open my database I get the legend:

ACCOUNTLIST_V1: Exception SQL logic error or missing database(1): no such column:STATEMENTLOCKED

So I shall have to roll back to the previous version, but any ideas anyone?

[Feanx]

Exactly the same thing has happened to me. When I try to open my database I get the legend:

ACCOUNTLIST_V1: Exception SQL logic error or missing database(1): no such column:STATEMENTLOCKED

So I shall have to roll back to the previous version, but any ideas anyone?

For me, downgrading to the previous version has worked.
The database is not corrupted, it's just that MMEx 1.3.1 cannot read something in it...

[GabrieleV]

https://sourceforge.net/p/moneymanagerex/bugs/927/

[Feanx]

Thank you so much !

[jandry]

It seems I have a similar issue.
I have my db en google drive, I was able to open it with Android and 1.2.7 version.
I just upgraded to 1.3.1 on my Windows, it's crashing when opening my db. (32bit or 64 bit version). Crash has not same behaviour. I have no error on screen and crash report also crash.

I don't find a download link for 1.2.7 to revert (I try 1.3.0 alpha and I got same issue)

How can I solve the issue ?

[jandry]

I found the 1.2.7, and I can reopen my database

[apeman]

Thanks GabrieleV, I applied the patch and all well and good again using 1.31. Again, many thanks for the pointer.

[gropasis2]

thanx the pach worked 

[jandry]

thanx the pach worked 

I don't understand how to apply the patch... In 1.3.1 I can run the patch on a newly created db but not on my 1.2.7 db because it crashes the application when I start it


Has somebody a solution on this

[GabrieleV]

If MMEX crashes unfortunately you cannot apply patch.

Patches are for very specific problems, a patch that it's not designed for your error could corrupt your DB.

Please try version 1.3.2 or 1.3.3, under some circumstances there was a bug in 1.3.1 that causes application crash.

[corse63]

If MMEX crashes unfortunately you cannot apply patch.

Patches are for very specific problems, a patch that it's not designed for your error could corrupt your DB.

Please try version 1.3.2 or 1.3.3, under some circumstances there was a bug in 1.3.1 that causes application crash.

Version 1.32 does not work, same behaviiour BTW when I tried 1.34, the install file shows 1.34 but once installed it appears as 1.31...., and crashes as well when opening DB

[naskoistaken]

I don't seem able to apply the patch.

I'm obviously doing something wrong, as when I try to navigate to the check.mmdbg file, the 'Load file' dialog won't list the two files when I point to their location folder.

I've renamed them manually to check.mmdbg and patch.mmdbg, but alas - the load file dialog won't list them.

My setup:

Ubuntu Xenial 16.04
MMEX 1.4.0-Alpha (DB v.7)
wxWidgets 3.0.2
SQLite3 3.14.1
wxSQLite3 3.4.0
Mongoose 6.5
Lua 5.2
GNU GCC/G++ 5.4.0 20160609

[corse63]

Since I had no answer, the workaround I used was to export a QIF file from 1.27 and import it in 1.33. Painful but it works

[Nikolay]

Since I had no answer, the workaround I used was to export a QIF file from 1.27 and import it in 1.33. Painful but it works

That was smart!