#389 MoneyManagerEx 1.0.0.3 DEV:SVN-6230 (Win 32bit)

[Simon Duane]

On deleting either/both of the two Stocks accounts from my database, MMEX immediately throws a

MoneyManagerEx Error
ACCOUNTLIST_V1: 7 not found

The Details>> view shows that this is the last of 80 or more such errors.

as it displays the Home Page. The error recurs every time the database is opened.

I haven't previously tried to delete a Stocks account, so this issue may not be new to version 1.0.0.3)

[guanlisheng]

Follow the steps to delete the dirty data
http://forum.moneymanagerex.org/viewtopic.php?f=5&t=5454

[Simon Duane]

I downloaded and ran SQLite but my database is encrypted, and it appears that sqlite does not support encryption.
Suggestions welcome.
Thanks

[guanlisheng]

I think you can convert the database to non-encrypted one.

On 14-6-17 20:12, "Simon Duane" sduane@users.sf.net wrote:

I downloaded and ran SQLite but my database is encrypted, and it appears
that sqlite does not support encryption.
Suggestions welcome.
Thanks

---

[bugs:#389] MoneyManagerEx 1.0.0.3 DEV:SVN-6230 (Win 32bit)

Status: open
Group: 1.1.0
Created: Tue Jun 17, 2014 07:14 AM UTC by Simon Duane
Last Updated: Tue Jun 17, 2014 08:58 AM UTC
Owner: nobody

On deleting either/both of the two Stocks accounts from my database, MMEX
immediately throws a

MoneyManagerEx Error
ACCOUNTLIST_V1: 7 not found

The Details>> view shows that this is the last of 80 or more such errors.

as it displays the Home Page. The error recurs every time the database is
opened.

I haven't previously tried to delete a Stocks account, so this issue may
not be new to version 1.0.0.3)

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/moneymanagerex/bugs/389/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[Stefano]

Using MMEX, open your encrypted database, then use: File ->Save Database As
Select mmb. This will create a copy and remove the encryption to your new database.

Correct the problem to the unencrypted version.

When all is well, re-encrypt your database as above, with a new name and selecting emb (encrypted).
When all is well delete the unencrypted database.

If something goes wrong, go back to your original encrypted file and start again.

[Gabriele]

On Windows you can use freeware SQLite2009 Pro that supports also encrypted database