mbeenham wrote:Does fixing the bug in the report also need some form of formal request?

No, you don't need to. I'm already looking at it, and I have a draft for a fix on my box. I am just going to take a couple of days to take a look at it and make sure it works. I'm going through some personal issues, so I want to make sure I don't commit anything without having a long look at it, trying not to break anything with this fix.

Thanks for your response - please take your time, this is not a big issue for me and in no way impacts on what I need to do with KMyMoney -everything is work-roundable.

The support in this forum is outstanding.
The application is outstanding.
I do not regret upgrading to KMyMoney from MSMoney.
I only regret not doing it sooner...

mbeenham wrote:The support in this forum is outstanding.
The application is outstanding.
I do not regret upgrading to KMyMoney from MSMoney.
I only regret not doing it sooner...

I just had to drop this here: http://kmymoney2.sourceforge.net/user-comments.html

Hei Ku wrote:No, you don't need to. I'm already looking at it, and I have a draft for a fix on my box. I am just going to take a couple of days to take a look at it and make sure it works. I'm going through some personal issues, so I want to make sure I don't commit anything without having a long look at it, trying not to break anything with this fix.

It is fixed in CVS now. You will have it available in the version 1.0 or a CVS package.

I just ran the report, first time in a while, and the problem seems to have gone so I guess your fix has made its way into the repository and one of the recent updates has installed it.

Thanks a lot for that, now all I need is a clean way of stopping EURO - GBP currency updates.