https://bugs.kde.org/show_bug.cgi?id=403608
--- Comment #2 from JAH ---
Thank you for such a prompt fix to this excellent application. I'm grateful for
the time and dedication the team put into maintaining and developing it and
have donated via KDE accordingly.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=403608
Bug ID: 403608
Summary: SaveAs defaults to "wrong" file path
Product: kmymoney
Version: 5.0.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=418479
Bug ID: 418479
Summary: Posting historical investment transactions causes
crash
Product: kmymoney
Version: 5.0.5
Platform: openSUSE RPMs
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=403608
--- Comment #3 from JAH ---
*** Bug 335804 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=418479
JAH changed:
What|Removed |Added
Summary|Posting historical |Kmymoney - Historical
|investment
https://bugs.kde.org/show_bug.cgi?id=418479
--- Comment #1 from JAH ---
This bug also creates a Data Consistency fault when saving work:
"The investment X has no price set for the Opening Date dd/mm/yy"
Normally entering the initial "Buy" transaction would also upda
https://bugs.kde.org/show_bug.cgi?id=335804
JAH changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=418479
--- Comment #4 from JAH ---
Thanks for the quick reply. I have tried my data using AppImage Kmymoney
Vn5.0.8 and problem recurs consistently with:
Investment Account A000362 Opened 01/01/2019
Security A000366 (and others A000367 A000368) OpeningDate
https://bugs.kde.org/show_bug.cgi?id=418823
--- Comment #5 from JAH ---
Thank you for addressing this issue. The Appimage version is a great way to
access the updated version prior to distro updates and this will return it to
full functionality for me. Many thanks.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=418479
--- Comment #8 from JAH ---
Created attachment 127384
--> https://bugs.kde.org/attachment.cgi?id=127384=edit
Anonomised data in support of bug description
Apologies for the delay in submitting this data
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=419519
JAH changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=419519
JAH changed:
What|Removed |Added
CC||vanques...@gmail.com
--- Comment #2 from JAH
https://bugs.kde.org/show_bug.cgi?id=418823
Bug ID: 418823
Summary: Script based online quotes not working
Product: kmymoney
Version: 5.0.8
Platform: Other
OS: Linux
Status: REPORTED
Severity: major
https://bugs.kde.org/show_bug.cgi?id=418823
--- Comment #1 from JAH ---
I should add that I only use this to import a csv file of prices in the format:
Symbol, price, date
and that if the CSV importer were able to handle that as an update to
kmm.prices it would be an ideal alternative to script
https://bugs.kde.org/show_bug.cgi?id=419519
Bug ID: 419519
Summary: Reports: Base Currency Conversions Incorrect
Product: kmymoney
Version: 5.0.8
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=421126
Bug ID: 421126
Summary: Securities Dialog "Market" field not populated with
existing data on edit
Product: kmymoney
Version: 5.0.5
Platform: openSUSE RPMs
OS:
https://bugs.kde.org/show_bug.cgi?id=421126
--- Comment #2 from JAH ---
Thanks for the tip re: .kmy files being compressed XML - I didn't know that.
Yes I'm sure the field has been populated in my database (even though it has no
default value as you point out).
To test for yourself:
1
https://bugs.kde.org/show_bug.cgi?id=421126
--- Comment #5 from JAH ---
Thank you for reviewing this issue and providing a fix.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433870
Bug ID: 433870
Summary: "To Amount" - Currency conversion function uses wrong
input value
Product: kmymoney
Version: 5.1.1
Platform: Appimage
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=448788
Bug ID: 448788
Summary: Incorrect Currency Conversion in Reports
Product: kmymoney
Version: 5.1.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: grave
https://bugs.kde.org/show_bug.cgi?id=473322
--- Comment #4 from JAH ---
Thanks so much for fixing this issue, it will make writing SQL queries so much
easier!
BTW am I right in thinking these ."valueFormatted" fields will no longer
include comma thousand separators (which prev
https://bugs.kde.org/show_bug.cgi?id=418479
--- Comment #14 from JAH ---
Sorry I've not been able to post for a while. This bug does indeed appear
resolve in kmymoney-5.1-291-linux-64-gcc.AppImage. Thank you.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=473322
--- Comment #6 from JAH ---
Thanks for your kind reply (and work on kmymoney).
I use the sqlite3 command to process preprepared .sql queries that produce .csv
reports with calculated ratios etc.
I noticed that prices (over 1000) stored
https://bugs.kde.org/show_bug.cgi?id=473322
--- Comment #8 from JAH ---
>>"I'll see if it's reasonable to add a checkbox to toggle the use of the
>>commas" -
That would be great if possible because as you say, I don't believe they have
any place in a numerical field. Sur
https://bugs.kde.org/show_bug.cgi?id=473322
Bug ID: 473322
Summary: SLQLite "kmmSplits"."sharesFormatted" Data Corrupt
perhaps??
Classification: Applications
Product: kmymoney
Version: 5.1.3
Platform: openSUSE
https://bugs.kde.org/show_bug.cgi?id=473322
--- Comment #10 from JAH ---
Well I'm very grateful for your consideration and raising the wish list entry.
Sorry I misunderstood your point about the function. As a complete amateur I
did try an extensive search for a solution / function but only came
26 matches
Mail list logo
