Hi all,

I've seen a couple of threads regarding consistency check errors being experienced under KMM 4.7.2, but I'm a bit confused as to what to do about them.

I imported a lot of historic data from another personal finance application into KMM when I first started to use it years ago (under version 0.9, if I remember correctly). I've had consistency check errors reported in that past due to problems with the old imported data, but it's all been working error-free for quite a while. However, immediately after upgrading from a problem-free KMM 4.7.1 to 4.7.2, I've started getting consistency check errors again. The first time I saved data under 4.7.2 I was notified of 193 problems, of which all but 64 were fixed automatically.

The 64 that remain seem to fall into two classes:-

The first appear right at the start of the error report, and are as follows:-

* Opening date of Account 'Opening Balances' cannot be changed to support transaction 'T000000000000000016' post date.
* Transaction 'T000000000000000016' has a post date '01/01/1990' before one of the referenced account's opening date.
Referenced accounts: Opening Balances
The post date was not updated to '01/05/1990'.
* Transaction 'T000000000000000018' has a post date '01/05/1990' before one of the referenced account's opening date.
Referenced accounts: Credit Card:Access (closed)
The post date was not updated to '01/10/1990'.

The second class of error is typically as follows:-

* The investment 'AstraZeneca plc' has no price set for the opening date '2010-10-19'.
Please enter a price for the investment on or before the opening date.
* The investment 'Sainsbury plc' has no price set for the opening date '2011-07-18'.
Please enter a price for the investment on or before the opening date.
* The investment 'National Grid' has no price set for the opening date '2011-07-18'.
Please enter a price for the investment on or before the opening date.
* The investment 'Aviva' has no price set for the opening date '1997-11-21'.
Please enter a price for the investment on or before the opening date.
* The investment 'Barclays plc' has no price set for the opening date '1997-07-07'.
Please enter a price for the investment on or before the opening date.

I saw a post on another thread indicating that the problem causing all the new consistency check errors experienced under 4.7.2 have been fixed, but that the fix hasn't been released yet.

Until that fix is released, can I ignore the errors that I'm seeing.... or is it better to fix the problems manually?

If the advice is to fix the errors, what do I have to do for the (what looks like) two different types of error reported in the above examples?

I've seen references to changing the relevant account opening date and I saw one post to the effect that the solution was to change the account opening date to "ages before the date of the failing transaction" (or words to that effect). I don't want to go around randomly tweaking dates in the hope that it will fix the problem, so can anyone tell me exactly what conditions are required in order to resolve the failing transactions/accounts such that the 4.7.2 consistency checker is happy again?

Finally, is there a planned or estimated release date for the coded fix?

Many thanks,

Mike

Welcome to 4.7.2 Mike

The first class of consistency checker output are easily fixed by setting the opening date of the ledger (Account->Edit Account->General Tab) on or before the first transaction date. The output of the consistency checker will tell you what ledgers and dates need to be changed. I simply set the affected ledger dates to 1/1/1990, well before my earliest transactions from 1993.

I imported transactions from MS Money five years ago and obviously the ledgers were created with an arbitrary date (date of import) instead of the date of the first transaction which is what the new consistency checker is now complaining about.

The second class of output are harder (take longer) to fix because for each investment you need to set an opening price on or before the first transaction date. All my investments begin with a buy transaction which is the opening price but its pretty time consuming to add that to the price history for each investment.

Since I had over 3000 of the first and 89 of the second I took the pragmatic decision to eliminate the 3000 odd reports of the first class which took less than a couple of hours and ignore the 89 second class which would have taken a great deal longer.

I am relatively comfortable in using 2.7.2 now I know that as long as the consistency checker output does not increment my data is OK.

Hopefully the consistency checker will deal with (automate) this basic stuff in due course.

Many thanks for your help.

Mike

Folks, came across this thread because I'm scratching my head on how to fix 14 consistency errors.
As an example, it says:


* Transaction 'T000000000000000016' has a post date '12/20/10' before one of the referenced account's opening date.
Referenced accounts: MyBankAccountName
The post date was not updated to '01/01/11'.


So, where the heck is this transaction? I'm looking and don't see any matches. I don't see any transactions that have a post date prior to an opening date.

EDIT - Okay, re-reading the thread. So, perhaps I should just change opening dates to something much earlier? Or is this part of the bug that is going to be fixed? If so, I'll simply wait.

If you open the account referenced and edit the account opening date to 12/20/10 (transaction post date) the consistency checker will be happy with this transaction.
You may even find the other 13 problem transactions will be resolved if they are all for the same account and for the same or later date.

If not just change the account opening (creation) date to the earliest transaction post date.

Its simply that no transaction post date should be earlier than the account opening date. The post date is probably correct so just change the opening date.
Mostly seems to happen when historical transactions are imported into an already created account.

Mbeenham, thanks. But KMyMoney won't let me change that date.

EDIT - Wait. I think I see now. Change the opening date in the account set up (Duh). I'll give it a try. Yep! that solved it! Only three problems left! Looks to be the same opening balance date problem. Just a matter of locating the correct account.

Thanks again!:)