Been running MMEX v 1.6.1 and thought I ought to get around to updating to latest version. But all versions above 1.6.1 fail with a v17 update error. v 1.62 fails with
I have looked through the forum and tried all update versions 1.6.2; 1.70, 1.80; 1.81 - none will update successfully (despite using fresh copies of my original db).
Is there a patch for this particular issue? If so where do I get it. Thanks!
Another old database failing to update to v17
Moderator: Renato
-
walker29
- New User
- Posts: 3
- Joined: Sat Dec 28, 2024 5:14 pm
- Are you a spam bot?: No
Another old database failing to update to v17
You do not have the required permissions to view the files attached to this post.
-
Renato
- MVP User
- Posts: 866
- Joined: Mon Apr 25, 2011 7:36 pm
- Are you a spam bot?: No
- Location: near Zurich
Re: Another old database failing to update to v17
If you like, you can send the .mmb to mmexregister@gmail.com and I will try to solve your problem.
Of course I guarantee the confidentiality of the data.
Of course I guarantee the confidentiality of the data.
Renato Forum Administrator (I'm not a developer)
-
walker29
- New User
- Posts: 3
- Joined: Sat Dec 28, 2024 5:14 pm
- Are you a spam bot?: No
Re: Another old database failing to update to v17
Thank you very much for the offer Renato - much appreciated. I have just sent you a small sanitised copy of my db which still fails to update.
I have previously checked for invalid records (found 2, fixed them, but that didn't solve the failure to import); likewise optimising tables.
One other option I have thought of is to export each account from v1.6.1 then import into a fresh db created in v 1.6.2
BUT... I have hit a snag there that I have a lot of records which are transfers between accounts. And it doesn't seem to handle this very well. Are there any plans to handle export and import of transfers in future updates?
I am guesing that main.[anything] is a joined view that isn't there normally, but gets created during the update process?
I have previously checked for invalid records (found 2, fixed them, but that didn't solve the failure to import); likewise optimising tables.
One other option I have thought of is to export each account from v1.6.1 then import into a fresh db created in v 1.6.2
BUT... I have hit a snag there that I have a lot of records which are transfers between accounts. And it doesn't seem to handle this very well. Are there any plans to handle export and import of transfers in future updates?
I am guesing that main.[anything] is a joined view that isn't there normally, but gets created during the update process?
-
Renato
- MVP User
- Posts: 866
- Joined: Mon Apr 25, 2011 7:36 pm
- Are you a spam bot?: No
- Location: near Zurich
Re: Another old database failing to update to v17
Many thanks for the DB.
However, it seems to me that this DB is not an original MMEX DB. The 13 bookings are from 2013, but have non-contiguous booking numbers 4753-4775, 4800-4882. In the database there are also tables that I can not explain, probably these were inserted / used by other programs (SQL).
I have deleted the tables sqlite_stat1 and sqlite_stat4, as well as the view income, then I was able to update to the latest MMEX version 1.9.0 Beta.
You can use https://sqlitebrowser.org/ to make these changes yourself.
However, it seems to me that this DB is not an original MMEX DB. The 13 bookings are from 2013, but have non-contiguous booking numbers 4753-4775, 4800-4882. In the database there are also tables that I can not explain, probably these were inserted / used by other programs (SQL).
I have deleted the tables sqlite_stat1 and sqlite_stat4, as well as the view income, then I was able to update to the latest MMEX version 1.9.0 Beta.
You can use https://sqlitebrowser.org/ to make these changes yourself.
Renato Forum Administrator (I'm not a developer)
-
walker29
- New User
- Posts: 3
- Joined: Sat Dec 28, 2024 5:14 pm
- Are you a spam bot?: No
Re: Another old database failing to update to v17
Many thanks Renato
The MMEX database was original, but I can't recall how old the earliest version I used was (c 2006 perhaps?) and that would proabbly have been imported from another app (MS Money??)
These were just a few ancient records I left in so the db had something of the original, but aren't contiguous as I deleted most of the existing records
I have used SQLite to view the database (and also to remove remaining payees and categories after I deleted most of accounts I had in it through MMEX. I also used another SQL viewer briefly before realising I'd downloaded the wrong app on my other computer!
That could have perhaps caused the sqlitestat tables as I don't recally them when I first viewed the db myself, but I've not created any tables myself.)
So the view income (and any sqlite-stat tables/views) are safe to delete - that's great. Many thanks, that is really appreciated
The MMEX database was original, but I can't recall how old the earliest version I used was (c 2006 perhaps?) and that would proabbly have been imported from another app (MS Money??)
These were just a few ancient records I left in so the db had something of the original, but aren't contiguous as I deleted most of the existing records
I have used SQLite to view the database (and also to remove remaining payees and categories after I deleted most of accounts I had in it through MMEX. I also used another SQL viewer briefly before realising I'd downloaded the wrong app on my other computer!
That could have perhaps caused the sqlitestat tables as I don't recally them when I first viewed the db myself, but I've not created any tables myself.)So the view income (and any sqlite-stat tables/views) are safe to delete - that's great. Many thanks, that is really appreciated