[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmymoney-devel
Subject:    [Kmymoney-devel] [Bug 246108] Consistency Check does not catch
From:       Russ Fineman <upscope () nwi ! net>
Date:       2010-08-20 22:42:35
Message-ID: 20100820224235.1D22B610D3 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=246108





--- Comment #9 from Russ Fineman <upscope nwi net>  2010-08-21 00:42:33 ---
Did some additional testing today.

If I edit the .kmy file and change the later T000000000000000001 transaction to
T123000000000000001, and then say save as database. it goes until the next
duplicate transaction (T000000000000000003) and give message for this
transaction. Changing it per above, it goes to next duplicate before error
again. I did not go any further but I assume it will eventually point out all
duplicates. I did not keep the changes until I here what effects it will have
and what your recommended solution is. In the mean time I can use the .kmy
local version instead of the MySQL database.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic