MMEX Discussion Forum

Hi

Have just belatedly upgraded my Windows version of MMEX to v 1.9.2

It upgraded my database

It is absolutely corrupted

Help please

Could you describe that in more detail?
Could you show us a list of the existing .mmb files?

Renato wrote: Fri Jun 12, 2026 9:02 pm Could you describe that in more detail?
Could you show us a list of the existing .mmb files?

Hi

I didnt take screen shots (before I reversed it all back to v1.8)

Is there some way to send you screenshots when I try the upgrade again??

Thanks

If you'd like me to help you, you'll need to provide a bit more detail about what happened after the update to 1.9.2.
From your previous posts, I can see that you were previously working with version 1.8.0.

Your .mmb database is likely stored in the cloud, since you also mentioned that you’re using the iOS version—which one?
By the way, if you’re using different MMEX versions across Windows, Android, Linux, and iOS, you should make sure that the versions are compatible with each other—in other words, all 1.9.2.

If you’ve now reverted back to 1.8.0, you should actually be getting an error message, since your database is in the 1.9.2 format.
Please take a screenshot of your .mmb files sorted by date and upload it to the forum.

Alternative: Pack all .mmb files (including those with .bak and _upgrade_) into a .zip file and send the .zip to info@mmex.ch, and I’ll take a look at it. Of course, I’ll treat your data confidentially.

Hi

The reason why I updated to 1.9.2 on Windows was because I believe the issue I have in the IOS version was because it was an old DB schema and IOS required 1.9.2 data file

I absolutely reverted to a new install on 1.8 on my desktop (uninstalled 1.9.2 first then a reboot) and used a backup copy of the .mmb that hadnt been opened by 1.9.2 so its structure hadnt been modified at all

And that works.

Then I tried updating to 1.9.2 from within a running instance of 1.8, opened the data file, it corrupted several accounts quite badly.

I also tried updating to 1.9.2 directly by downloading the installer and installing via that. Same problem

Both methods produced exactly the same corruption in the data file - same accounts, same transactions.

I will zip up and email screen shots of what it looked like in 1.8 and what it looks like after DB upgrade to 1.9.2

Going forward I dont intend to use the IOS version on-line connected to a cloud - when travelling I dont always have connection to the internet so was wanting to keep track of money by downloading the latest database to my iPAd, using mmex there to record transactions in a "disconnected" mode, and then when I return I'll upload the data file back to my dekstop verison and carry on using it from there.

Many thanks for your help

Hi Renato

I think I have solved it ..... I have no idea why but when my 1.8 db was upgraded to 1.9.2, for every account a payee filter has been set so each account was only showing a randomly chosen set of transactions.

Could that be possible?