Any time I save the check consistency report me 2 errors that can not be solved.

* The date of opening of the account "Sales initial" can not be changed to support the posting date of the transactions' T000000000000000001. "
   * The transaction "T000000000000000001" has a posting date "03/12/2009" before one of the dates of your account reference.
     Counts of references: Initial Sale
     The posting date has not been updated to "7/12/2009".

Finished: 0 problems corrected. 2 problems still present.

I tried to change the date of all account without success. I don't know what else I can do but I don't want to see this error messagge anymore.

Anyone can help me please !!???

Have you checked the transaction in that date and all accounts, even the closed ones, have the correct opening date?

Yes. I set all the account I can find to the correct date.

Have you checked your settings to show closed accounts too?
And, to show equity accounts too.

Other than that, the only other thing I can think of is to actually open the file to see which are the accounts involved in that transaction.

YEEESSS !!!

It was because of hidden equity accounts.

Thank you very much !!!!

Today my Linux Mint Update Manager advised me that KMM v4.7.2 [finally, thanks Clay] was available in the PPA, so i happily accepted it & upgraded my 4.7.1 to 4.7.2. Upon opening my data file, all looked fine & normal. Several minutes later i got a fright, when a separate window opened up on-screen, apparently for the Consistency Check, reporting 34 errors, which it then claimed to have fixed. Here's just a small sample [account names removed]:

* Transaction 'T000000000000000001' post date '1990-01-08' is older than opening date '2012-03-04' of account '<< snip >>'.
Account opening date updated.
* Transaction 'T000000000000000002' post date '1990-01-08' is older than opening date '2012-03-04' of account '<< snip >>'.
Account opening date updated.
* Transaction 'T000000000000000022' post date '1998-04-28' is older than opening date '2012-04-09' of account '<< snip >>'.
Account opening date updated.
* Transaction 'T000000000000000023' post date '1998-04-28' is older than opening date '2012-04-09' of account '<< snip >>'.
Account opening date updated.
* Transaction 'T000000000000000024' post date '1998-04-28' is older than opening date '2012-04-09' of account '<< snip >>'.
Account opening date updated.
* Transaction 'T000000000000000026' post date '1998-04-29' is older than opening date '2012-03-31' of account '<< snip >>'.
Account opening date updated.
more of these, then...
Finished: 34 problems corrected. 0 problems still present.

Very alarmed, i checked several of these items randomly but they seemed ok to me [ie, it seems that KMM's "corrected" did not do any obvious damage]. However i do not understand why this happened, what it means, why it happened suspiciously soon after the upgrade, if any damage really did occur, & if i should now do... something.

Can someone pls advise me? Ta.

steffie wrote:Can someone pls advise me? Ta.

No harm has beed done, this was a step to adjust account opening dates according to dates of the transactions that are contained in the account. As you may know the UI does now allow you to add transactions to an account prior to it's opening date, this check was not performed during import of old data. The consistency check just fixes this be adjusting the opening date of the account to the post date of the oldest transaction in that account.

I have just this morning upgraded from 2.7.1 to 2.7.2 and am now getting a report from the consistency checker across multiple transactions (over 3000 of them) in multiple accounts which are not being automatically corrected

* Transaction 'T000000000000000002' has a post date '29/07/1992' before one of the referenced account's opening date.
Referenced accounts: X Accounts:Jack Loan
The post date was not updated to '08/06/2009'.

[Snipped for brevity]

* The investment 'INTERCONTL HOTELS ORD GBP0.13617' has no price set for the opening date '2010-11-16'.
Please enter a price for the investment on or before the opening date.

Finished: 0 problems corrected. 3,086 problems still present.

With this number of uncorrected "problems" I am obviously considering my options and in order of my preference:
1) Revert to 2.7.1
2) Ignore
3) Fix

I don't think 3) is really an option unless it can be automated as I don't have unlimited time on my hands.
Any informed advice really appreciated
Many thanks,
Martin

mbeenham wrote:I don't think 3) is really an option unless it can be automated as I don't have unlimited time on my hands.
Any informed advice really appreciated

3,086 is the number of transactions in this situation, you only need to edit the accounts that contain these transactions (there should be a lot less) and fix their opening dates manually. If you have too many accounts let us know and we can think of another solution.

Oh phew, thank you cristian.

I don't have the time at present to go through and fish out all the accounts that need updating from the consistency checker output so would like to roll back to 4.7.1.

Anyone know where I can get this? Only 4.7.2 and 4.6.4 are showing from the ppa.

Thanks

OK, I needed to use KMyMoney so downgraded to 4.6.4 no problem.
Data reports consistent again
Will keep with this version until I've time to go through my accounts and find transactions that confuse the consistency checker in 4.7.2.
It would be great if the output of the consistency checker was in csv format so that I could easily import into a spreadsheet...