Hi,

For a while now, whenever I save my KMyMoney file the consistency checker has been reporting six errors. It is saying that six investments have no price set for the opening date. These errors started spontaneously quite a few months ago. I've ignored them to date because they all relate to long-ago closed accounts that all have a zero balance and none of which contain any currently held investments. However, I recently upgraded to Ubuntu 12.04 and KMyMoney 4.6.3 so I thought now would be a good time to clean-up these errors. The odd thing is that the "opening dates" that supposedly have the missing prices are in no way related to the dates during which these investments were held. In most if not all cases, the "opening date" reported in the error message as having no price is long after the last transaction in the affected accounts and long after the account was closed.

Given that the errors are quoting dates that don't fit logically with the accounts/investments in question, I'm wondering how to fix this problem. In other words there doesn't seem much point in entering a price for an investment on 31/10/2008 when the investment was sold and the account closed two or three years earlier.

Any ideas as to what might be causing this?

Thanks

Mike

Is there any stock created on that date? It's really weird that it reports an error for a date with no transactions

There may well be... but finding it could be tricky due to the number of accounts involved. Is there an easy way to find it via a search of the KMyMoney file, rather than trying to use the application to do it manually. Unfortunately I don't yet use a database backend...

Mike

Just to clarify my last reply....

There is no stock created on the date in question for the account against which the error was logged. But there may be some different stock created on the date in question in some other account.

That's a bug. Could you file a bug in bugs.kde.org and upload an anonimized file to the bug so we can test what's wrong?

OK, I'll get that done over the next couple of days.

A bit more info....

An investment report covering the date in question reveals just a single transaction - a dividend payment - but it's for a completely different stock in a completely different account.

I should add that the report didn't include the closed accounts that supposedly cause the error. But all those closed accounts are correctly reconciled and have zero closing value so it seems unlikely that an "extra" transaction could have found its way in there to cause the problem?

Thanks for your help.

It's not likely. It's most likely a bad check on the price date for the opening dates, and then reporting it badly.

Bug raised as requested.