https://bugs.kde.org/show_bug.cgi?id=272398
--- Comment #10 from Dennis Gallion <dwgall...@gmail.com> --- Thank you Thomas for your help. I think I found the source of the problem and have resolved it: At first run the consistency log showed 185 errors corrected; 5458 could not be corrected. The problem was apparently created when I first set up KMyMoney on 6/10/2007 and performed a conversion import from IIRC the Windows application I had been using (I don't recall whether I used qif or csv). The accounts all had an opening date of 6/10/2007, whereas there were transactions in some accounts dating back to 1/2/1998. Using the largest account, I edited its opening date to 12/31/1997. The consistency log then showed the number of uncorrected errors reduced to 1841; all errors for that account were resolved. I used this process for the additional accounts, one at a time, editing the opening date to be a couple days before the earliest transaction for that account. Following each account opening date change, I re-ran the consistency report. The number of errors reduced from 1841 to 346, then to 33, then to 0. So in summary apparently the errors are caused by transaction dates being earlier than the account opening date. Since 185 errors were corrected, I suspect that the program auto corrects such errors when they are only within a specific time window. Btw, when I attempted to change the account opening date by manual entry, the screen would not permit it. I needed to use the associated calendar and scroll back to the older date; the change was then accepted. The solution of course is for the user at setup, if doing an import conversion, to ensure that the account opening date is older than the oldest imported date, rather than the setup date. I have sent to your email address the anonymous file you requested, and a copy of each consistency log file as I went through the process described above. Thanks again for your and Alan's assistance. I really like KMyMoney! -- You are receiving this mail because: You are watching all bug changes.