[kmymoney] [Bug 427590] New: Edit P: cannot input negative amount
https://bugs.kde.org/show_bug.cgi?id=427590 Bug ID: 427590 Summary: Edit P: cannot input negative amount Product: kmymoney Version: git (master) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: t...@marshall.name Target Milestone: --- Version: 5.0.80-d8b7b6b0c SUMMARY When editing splits of a transaction, I try to enter a negative amount into a split; however, when I press enter or click the tick, its value changes to a positive value. STEPS TO REPRODUCE 1. Insert a transaction and click the Splits button 2. Enter a transaction in the split window, with a negative amount. 3. Click the tick, or press Enter to finish editing OBSERVED RESULT The sign of the amount changes to a positive value. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 427590] Edit P: cannot input negative amount
https://bugs.kde.org/show_bug.cgi?id=427590 --- Comment #1 from Tony --- CORRECTION: The version is 5.1.0-2a911c86b. The version in the original description (5.0.80-d8b7b6b0c) has the correct behaviour. (I rolled back to that version in order to enter the splits correctly.) -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney4] [Bug 364425] CSV import only shows checking accounts when selecting Banking
https://bugs.kde.org/show_bug.cgi?id=364425 --- Comment #10 from Tony --- It has been over a year since the last release of KMyMoney and since this bug was reported. When will a new version with the fix be released? -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 400464] New: On startup a foreign image is loaded to the screen (the image is actually an output image from qgis). Kmymoney operations seem to remain, but are unuseable as any informat
https://bugs.kde.org/show_bug.cgi?id=400464 Bug ID: 400464 Summary: On startup a foreign image is loaded to the screen (the image is actually an output image from qgis). Kmymoney operations seem to remain, but are unuseable as any information displayed is shown below the image, and scrolls off the screen. Product: kmymoney Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: to...@sa.apana.org.au Target Milestone: --- Created attachment 115971 --> https://bugs.kde.org/attachment.cgi?id=115971&action=edit Screendump of opening screen SUMMARY On startup a foreign image is loaded to the screen (the image is actually an output image from qgis). Kmymoney operations seem to remain, but are unusable as any information displayed is shown below the image, and scrolls off the screen STEPS TO REPRODUCE 1. Start my money from the command line in order to obtain startup messages 2. 3. Konsole output: Startup messages are below; Note I'm using Nightly build #170 which worked without problem, allowing normal operation (including edting data and a number of open and close cycles). The current problem seems spontaneous tonbaz@muscat3:~$ opt/kmm/kmymoney--d0e7eea-x86_64.appimage QPainter::begin: Paint device returned engine == 0, type: 2 WebConnect: Try to connect to WebConnect server WebConnect: Connect to server failed WebConnect: Running in server mode QFSFileEngine::open: No file name specified Plugins: budgetview loaded Plugins: checkprinting loaded QIODevice::read (QFile, "/usr/share/checkprinting/check_template.html"): device not open Plugins: csvexporter loaded Plugins: csvimporter loaded Plugins: forecastview loaded Plugins: gncimporter loaded Plugins: icalendarexporter loaded Plugins: kbanking loaded 3:2018/10/30 08-56-10:gwen(2556):/home/appimage/appimage-workspace/deps-build/ext_gwenhywfar/ext_gwenhywfar-prefix/src/ext_gwenhywfar/src/base/plugin.c: 379: Plugin "dir" not found. 3:2018/10/30 08-56-10:(null)(2556):/home/appimage/appimage-workspace/deps-build/ext_aqbanking/ext_aqbanking-prefix/src/ext_aqbanking/src/libs/aqbanking/banking_cfg.c: 77: Could not create ConfigMgr[dir:///home/tonbaz/.aqbanking/settings]. Maybe the gwenhywfar plugins are not installed? 3:2018/10/30 08-56-10:(null)(2556):/home/appimage/appimage-workspace/deps-build/ext_aqbanking/ext_aqbanking-prefix/src/ext_aqbanking/src/libs/aqbanking/banking_cfg.c: 100: No config manager. Maybe the gwenhywfar plugins are not installed correctly? KBankingPlugin: No AqB4 config found. KBankingPlugin: No AqB3 config found. 3:2018/10/30 08-56-10:aqbanking(2556):/home/appimage/appimage-workspace/deps-build/ext_aqbanking/ext_aqbanking-prefix/src/ext_aqbanking/src/libs/aqbanking/banking_cfg.c: 712: No config manager. Maybe the gwenhywfar plugins are not installed correctly? Error on online init (-1). Could not initialize KBanking online banking interface Plugins: ofximporter loaded Plugins: onlinejoboutboxview loaded Plugins: qifexporter loaded No such XML file "/tmp/.mount_kmymonbbSgam/usr/bin/../share/kxmlgui5/csvexporter/qifimporter.rc" Plugins: qifimporter loaded Plugins: reconciliation report loaded Plugins: reportsview loaded Plugins: sqlstorage loaded Plugins: xmlstorage loaded Trying to convert empty KLocalizedString to QString. Stops to allow authenticatuion to postgresql database then: Cost center model created with items 0 Payees model created with items 0 Unknown view '' in slotOpenURL() OBSERVED RESULT EXPECTED RESULT SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 400464] On startup a foreign image is loaded to the screen (the image is actually an output image from qgis). Kmymoney operations seem to remain, but are unuseable as any information
https://bugs.kde.org/show_bug.cgi?id=400464 --- Comment #1 from Tony --- Seems to have something to do with the splash screen. The appimage is stored in $HOME/opt/kmm. If the splash screen box in General/Global is not selected Then using Konsole, starting from the $HOME directory invoking opt/kmm/appimgename the behaviour occurs. Using Dolphin and clicking the appimmage the behaviour disappears and normal startup occurs -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 400642] New: Cannot save after manual price entry
https://bugs.kde.org/show_bug.cgi?id=400642 Bug ID: 400642 Summary: Cannot save after manual price entry Product: kmymoney Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: database Assignee: kmymoney-devel@kde.org Reporter: to...@sa.apana.org.au Target Milestone: --- SUMMARY: Manual price entry worked as expected. Multiple price entries can be accepted. On saving an error occurred: STEPS TO REPRODUCE 1. Enter a price for a security through the Exchange rate/price editor 2. Click on File- Save OBSERVED RESULT 3. A window appears titled Error-Kmymoney, with the message faild to save your storage. 4: message datas are: Error in function void MyMoneyStorageSqlPrivate::writeFileInfo() : writing FileInfo Driver = QPSQL, Host = localhost, User = tonbaz, Database = kmymoney Driver Error: Database Error No -1: Text: Error type 0 Executed: UPDATE kmmFileInfo SET version = ?, fixLevel = ?, created = ?, lastModified = ?, baseCurrency = ?, dateRangeStart = ?, dateRangeEnd = ?, hiInstitutionId = ?, hiPayeeId = ?, hiTagId = ?, hiAccountId = ?, hiTransactionId = ?, hiScheduleId = ?, hiSecurityId = ?, hiReportId = ?, hiBudgetId = ?, hiOnlineJobId = ?, hiPayeeIdentifierId = ?, encryptData = ?, updateInProgress = ?, logonUser = ?, logonAt = ?, institutions = ?, accounts = ?, payees = ?, tags = ?, transactions = ?, splits = ?, securities = ?, prices = ?, currencies = ?, schedules = ?, reports = ?, kvps = ?, budgets = ?; Query error No 22003: ERROR: bigint out of range (22003) QPSQL: Unable to create query Error type 2 /home/appimage/workspace/KMyMoney_Nightly_Appimage_Build/kmymoney/kmymoney/plugins/sql/mymoneystoragesql_p.h:802 EXPECTED RESULT Normal saving action SOFTWARE VERSIONS KDE Frameworks 5.51.0 Qt 5.11.2 (built against 5.11.2) The xcb windowing system ADDITIONAL INFORMATION Using nightly build #72 -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 400642] Cannot save after manual price entry
https://bugs.kde.org/show_bug.cgi?id=400642 --- Comment #1 from Tony --- Using postgresql 10 back end -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 401927] Unable to add new investment
https://bugs.kde.org/show_bug.cgi?id=401927 Tony changed: What|Removed |Added CC||to...@sa.apana.org.au --- Comment #1 from Tony --- Thanks for reporting this problem. I have an almost identical result, giving an error message "Unable to create all objects for the investment" with no further detail, except that the application does not crash Using Kmymoney 5.0 KDE Plasma version 5.12.7 KDE Frameworks 5.44.0 Qt 5.9.5 (built against 5.9.5) The xcb windowing system Kubuntu 18.04.1 LTS Kubuntu -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 401927] Unable to add new investment
https://bugs.kde.org/show_bug.cgi?id=401927 --- Comment #4 from Tony --- It's occurring using the xml back end Tony -- You are receiving this mail because: You are the assignee for the bug.
[Kmymoney-devel] [Bug 272398] New: KMyMoney 4.5.2 (KDE 4.5.5) Ubuntu 10.10 slowed and is now consistently slow in edit Ledger Entry (Transaction)
https://bugs.kde.org/show_bug.cgi?id=272398 Summary: KMyMoney 4.5.2 (KDE 4.5.5) Ubuntu 10.10 slowed and is now consistently slow in edit Ledger Entry (Transaction) Product: kmymoney4 Version: 4.5.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kmymoney-devel@kde.org ReportedBy: acellisscan-softw...@yahoo.co.uk Version: 4.5.2 (using KDE 4.5.5) OS:Linux KMyMoney has become very slow when editing (or cancelling the edit) of a Ledger entry. Reproducible: Always Steps to Reproduce: Easily reproduced but do not know what triggered the degradation. System monitor shows high CPU utilisation. However this is a new machine 4 core AMD phenom2 965 with 8GB. Noticed some posts relating to video so thought View | Show Transaction Detail might be relevant. Ran with debug timers and found significant difference - factor of 10X. See below Actual Results: Edit and then Cancel Ledger entry with Show transaction detail on: Timer(Start adjusting column 0): 53441 elapsed Timer(Start adjusting column 6): 89 elapsed Timer(Start adjusting column 7): 126 elapsed Timer(Start adjusting column 11): 78 elapsed Timer(Start adjusting column 0): 186 elapsed Timer(Start adjusting column 6): 88 elapsed Timer(Start adjusting column 7): 127 elapsed Timer(Start adjusting column 11): 78 elapsed Timer(Update register): 40873 elapsed Timer(Done updateing register): 0 elapsed Timer(Update register): 3531 elapsed Timer(Done updateing register): 5122 elapsed Timer(Update register): 293 elapsed Timer(Done updateing register): 0 elapsed Timer(Update register): 2460 elapsed Timer(Done updateing register): 5088 elapsed Now with Show transaction detail OFF: Timer(Update register): 35329 elapsed Timer(Done updateing register): 1 elapsed Timer(Update register): 178 elapsed Timer(Done updateing register): 2385 elapsed Timer(Update register): 10 elapsed Timer(Done updateing register): 584 elapsed Timer(Start adjusting column 0): 23 elapsed Timer(Start adjusting column 6): 55 elapsed Timer(Start adjusting column 7): 81 elapsed Timer(Start adjusting column 11): 50 elapsed Timer(Update register): 123 elapsed Timer(Done updateing register): 0 elapsed Timer(Update register): 156 elapsed Timer(Done updateing register): 0 elapsed Timer(Update register): 4871 elapsed Timer(Done updateing register): 628 elapsed Timer(Update register): 142 elapsed Timer(Done updateing register): 0 elapsed Timer(Update register): 2216 elapsed Timer(Done updateing register): 600 elapsed OS: Linux (x86_64) release 2.6.35-28-generic Compiler: cc Ubuntu 10.10 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
Re: [kmymoney] [Bug 353555] Database backend is much slower than standard kmy format
On 28/03/2021 14:15, jesse wrote: > https://bugs.kde.org/show_bug.cgi?id=353555 > > --- Comment #9 from jesse --- > I still have not had time to try to figure out if the database has indexes or > not. I don't use the application with the database option. > > >From what Martin said, the real need is based on using external programs to > query the sqlite database. Without a way to know all the use cases, it may be > best to either include documentation in the manual as to how and when a user > would want to add indexes for their querying, or to add a few indexes to help > our 80% of the use cases. > > However, I think the decision should be made as to whether saving to the > sqlite > format was intended for this purpose or not. > > If not, then perhaps there are no further changes required. > As the original developer of the database module, my main reason for producing it was the ability to extend the functionality of KMM for my own purposes Using mysql rather than sqlite, I have triggers and routines and extra tables which enable me to do my annual tax return in a day rather than a week. My design didn't require any indexes, and since the initial method of operation was, as now, load the database and save it on exit, there didn't seem to be much need for them. Later the code was improved (not by me) to use the database in the conventional sense, committing updates to the database as they occurred. In that case, indexes were added to speed up the process. Unfortunately, a later rewrite reverted to the load/save method, where offhand I can't really see much need for indexing. -- Cheers TonyB
Re: Error Connecting to MySQL DB 4.8.1.1
As the original developer of the DB interface, I'm interested in this thread. I had a similar problem to the OP when I tried 4.8 under Windows, but when I tried looking a bit at the code, I found it had changed so much since I was last involved, and unfortunately didn't have much time available to try relearning! But as a general point, the original design tried to distinguish between application version updates and database version changes (though normally these would go step in step). To this end, the kmmFileInfo table contains a 'version' and a 'fixlevel' column; IIRC, the former indicated the database version and the latter corresponds to the application version. If the database layout changes in any way, the database version number should be updated. When an existing database is opened, the database manager should detect the change in version and create/delete/alter any tables/columns as required. As for naming a column 'order', I'm at a loss to understand how that worked, because I'm pretty sure that's a reserved word in all versions of SQL! -- Cheers TonyB
Re: Error Connecting to MySQL DB 4.8.1.1
The problem with the keyword 'order' is that, although it has been escaped, the character used is a double-quote. By default, Mysql doesn't recognize this; it expects a backtick as the escape character. If you have access to the Mysql configuration, this can be fixed by the addition of the line sql_mode = 'ANSI_QUOTES' to the [mysqld] section of the configuration file (in ubuntu, at /etc/mysql/mysql.conf.d/mysql.cnf), and restarting the mysql server. With this fix, I was able to load my 4.6 anonymized file under 4.8.0 in about 3-4 minutes. However, I decided to build 4.8.1.1 from source and try that. I got the following error loading my 4.6 file: - Error in function bool MyMoneyStorageSql::alterTable(const MyMoneyDbTable&, int) : Error inserting into new table kmmFileInfo Driver = QMYSQL, Host = localhost, User = tonyb, Database = Anonkmm Driver Error: Database Error No -1: Text: Error type 0 Executed: INSERT INTO kmmFileInfo (version, created, lastModified, baseCurrency, institutions, accounts, payees, tags, transactions, splits, securities, prices, currencies, schedules, reports, kvps, dateRangeStart, dateRangeEnd, hiInstitutionId, hiPayeeId, hiTagId, hiAccountId, hiTransactionId, hiScheduleId, hiSecurityId, hiReportId, encryptData, updateInProgress, budgets, hiBudgetId, '', '', logonUser, logonAt, fixLevel) SELECT version, created, lastModified, baseCurrency, institutions, accounts, payees, '', transactions, splits, securities, prices, currencies, schedules, reports, kvps, dateRangeStart, dateRangeEnd, hiInstitutionId, hiPayeeId, '', hiAccountId, hiTransactionId, hiScheduleId, hiSecurityId, hiReportId, encryptData, updateInProgress, budgets, hiBudgetId, '', '', logonUser, logonAt, fixLevel FROM kmmtmpFileInfo; Query error No 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''', '', logonUser, logonAt, fixLevel) SELECT version, created, lastModified, bas' at line 1 QMYSQL: Unable to execute query Error type 2 This looks pretty bad! I downloaded the source from one of the mirrors on this page: https://download.kde.org/stable/kmymoney/4.8.1.1/src/kmymoney-4.8.1.1.tar.xz.mirrorlist If someone can confirm that is the latest, I'll look into the problem if you wish. -- Cheers TonyB
Re: [kmymoney] [Bug 392755] New: kmymoney-4.8.1.1 suggestion: Category for realized profit/loss of an investment
On 05/04/18 13:17, Christian wrote: > https://bugs.kde.org/show_bug.cgi?id=392755 > > Bug ID: 392755 >Summary: kmymoney-4.8.1.1 suggestion: Category for realized > profit/loss of an investment >Product: kmymoney >Version: 4.8.1 > Platform: Gentoo Packages > OS: Linux > Status: UNCONFIRMED > Severity: normal > Priority: NOR > Component: general > Assignee: kmymoney-devel@kde.org > Reporter: gen...@moin.fi > Target Milestone: --- > > Suggestion: When selling an investment, calculate the realized profit or loss > and assign a category to it. > > Motivation: It would be nice to have the investment "returns" in a category, > so > that they show up in the Income/Expenses views. Also, for the accounting, > where > the balance sheet shows the current state of all assets, and the difference > from one year to the next is captured in the categories (Income, Expenses), > there has to be a category where this realized profit/loss is captured, > otherwise the differences in the balance sheet and in the "bottom-line" of the > income-expenses do not match. > > Implementation: I think that this realized profit/loss is usually calculated > by > tracking the purchasing price of the oldest asset still held. > > Example 1: > 1.1.2016 Buy 10 shares of XYZ at 5 per share (transaction value 50) > 1.1.2017 Buy 5 shares of XYZ at 7 per share (transaction value 35) > 1.1.2018 Sell 15 shares of XYZ at 9 per share (transaction value 135) > --> Here, the purchase value was 85, the sales value 135, i.e. a profit of 50. > There should be a category where this is shown as 50. > > Example 2: > 1.1.2016 Buy 10 shares of XYZ at 5 per share (transaction value 50) > 1.1.2017 Buy 5 shares of XYZ at 7 per share (transaction value 35) > 1.1.2018 Sell 5 shares of XYZ at 9 per share (transaction value 45) > --> This would be a profit of 20 because those 5 shares were bought 1.1.2016 > at > price 5. There should be a category where this is assigned to. > 1.3.2018 Sell 10 shares of XYZ at 10 per share (transaction value 100) > --> This would be a profit of 40 because 5 shares were bought 1.1.2016 and 5 > on > 1.1.2017. > Would that work? Aren't you counting the amount of money you received for the shares as income, then counting part of it again as profit? -- Cheers TonyB
Re: [kmymoney] [Bug 390411] Sqlite opening broken
On 02/05/18 05:38, sergio_nsk wrote: > https://bugs.kde.org/show_bug.cgi?id=390411 > > sergio_nsk changed: > >What|Removed |Added > > CC||sergio_...@yahoo.de > > --- Comment #3 from sergio_nsk --- > I have the same problem. Tried to open sqlite database used in kmymoney 4.8 > from a command line in Ubuntu Bionic: > I'm working on this. -- Cheers TonyB
[kmymoney] [Bug 409237] New: Wrong data in databsae splits record
https://bugs.kde.org/show_bug.cgi?id=409237 Bug ID: 409237 Summary: Wrong data in databsae splits record Product: kmymoney Version: git (master) Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: database Assignee: kmymoney-devel@kde.org Reporter: tonyb...@ntlworld.com Target Milestone: --- SUMMARY When a split is stored in a database, the sharesFormatted field contains the price rather than the share count. STEPS TO REPRODUCE 1. Store transactions in a database. 2. Using SQL, examine the kmmSplits records, columns shares and sharesFormatted. OBSERVED RESULT The sharesFormatted column always contains a formatted version of the price column EXPECTED RESULT The columns should contain a formatted version of the shares column. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 19.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 409237] Wrong data in database splits record
https://bugs.kde.org/show_bug.cgi?id=409237 Tony Bloomfield changed: What|Removed |Added Summary|Wrong data in databsae |Wrong data in database |splits record |splits record -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 409614] New: Share price precision incorrectly limited to 4 decimal places
https://bugs.kde.org/show_bug.cgi?id=409614 Bug ID: 409614 Summary: Share price precision incorrectly limited to 4 decimal places Product: kmymoney Version: 5.0.4 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: tonyb...@ntlworld.com Target Milestone: --- Created attachment 121380 --> https://bugs.kde.org/attachment.cgi?id=121380&action=edit Screenshot4.6 SUMMARY In 5.0, share prices are rounded to a maximum of 4 decimal places. This is a regression from 4.6 (don't know about 4.8). Assume an investment of 5000.00 at a price of 3.146151 = 1589.2435 shares (this can happen with UK unit trusts aka mutual funds). The investemnt is created with a Fraction of 1 and prices precision of 6 decimal places. Screenshot4.6 shows the transaction entered in 4.6 with a correct total amount of 5000.00. Screenshot5.0 shows the same transaction imported into 5.0 where the price has been rounded to 3.1462, and an attempt to enter a similar transaction where the amount total amount shows as 5000.08 (until you try to edit it when it changes to 5000.07!). There seems to be no way to adjust this down to 5000.00 via fees etc, making it difficult to balance the books. STEPS TO REPRODUCE Use the attached kmy file and try to enter a transaction using the above figures. OBSERVED RESULT As described above EXPECTED RESULT As shown in screenshot4.6. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu Mate19.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The 2 transactions appear in XML as follows: -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 409614] Share price precision incorrectly limited to 4 decimal places
https://bugs.kde.org/show_bug.cgi?id=409614 --- Comment #2 from Tony Bloomfield --- Created attachment 121382 --> https://bugs.kde.org/attachment.cgi?id=121382&action=edit KMyMoney file to re-create problem -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 409614] Share price precision incorrectly limited to 4 decimal places
https://bugs.kde.org/show_bug.cgi?id=409614 --- Comment #1 from Tony Bloomfield --- Created attachment 121381 --> https://bugs.kde.org/attachment.cgi?id=121381&action=edit Screenshot5.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 409614] Share price precision incorrectly limited to 4 decimal places
https://bugs.kde.org/show_bug.cgi?id=409614 --- Comment #3 from Tony Bloomfield --- Note: in KMM4.6, price precision was specified globally via KMyMoney Settings. In 5.0, it is per investment. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 409614] Share price precision incorrectly limited to 4 decimal places
https://bugs.kde.org/show_bug.cgi?id=409614 --- Comment #4 from Tony Bloomfield --- I note that in the test file I attached, the price precision for the security was reset to 4; this was probably my fault! However, editing the security to change precision to 6 places makes no difference; the price is still rounded to 4 places, and the total value is still wrong. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 409614] Share price precision incorrectly limited to 4 decimal places
https://bugs.kde.org/show_bug.cgi?id=409614 --- Comment #11 from Tony Bloomfield --- Apologies for not having my system up-to-date; blame it on my unfamiliarity with git. I have now built 5.0.5, and see the following rather odd behaviour. Entering a new transaction with share count and price (6 places) as above, the total amount is calculated as 5000.08; when I the transaction, the displayed price changes to 3.146200. However, if I edit the transaction and re-enter the original price, the amount changes to the correct value of 5000.00 and remains so after clicking . Very weird! Screenshots available if needed. -- You are receiving this mail because: You are the assignee for the bug.
Re: kmymoney at mobile
On 23/11/2019 09:06, Thomas Baumgart wrote: > There was one user who worked on an Android application, but I don't remember > what the status of it is. I don't even remember who that was (have to dig in > the mail archive). > I can't remember the developer's name, but a very early version of his efforts was available on the web with the package name 'package com.vanhlebarsoftware.kmmdroid'. I contacted him about it a couple of years ago, and he said he had done further development but had to give up due to other pressures. He offered to pass a copy of his efforts to someone else provided they would undertake to actively work on it and support it. I felt my own knowledge of Java/Android was (and is) insufficient to take it on. -- Cheers TonyB
[Kmymoney-devel] [Bug 274435] importing gnucash makes payee from comment instead of corresponding account
https://bugs.kde.org/show_bug.cgi?id=274435 Tony B changed: What|Removed |Added CC||tonyb.sf...@ntlworld.com --- Comment #2 from Tony B 2011-05-31 11:08:59 --- I think this happens with data imported into Gnucash from bank statements. Try the 'Transaction Notes' import option as per manual extract below. Perhaps we should try to think of a better name for this option. Transaction Notes option Under some usage conditions, non-split GnuCash transactions may contain residual, often incorrect, memo data which is not normally visible to the user. When imported into KMyMoney however, due to display differences, this data can become visible. Often, these transactions will have a Notes field describing the real purpose of the transaction. If this option is selected, these notes, if present, will be used to override the extraneous memo data. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
[Kmymoney-devel] [Bug 267233] Reports doesn't care about my category-setting when using the database backend.
https://bugs.kde.org/show_bug.cgi?id=267233 Tony B changed: What|Removed |Added CC||tonyb.sf...@ntlworld.com --- Comment #5 from Tony B 2011-05-31 11:19:09 --- I tried with 4.4.4 and mysql and couldn't see any problem, except that transactions which were split, with some categories deselected in the configure, would still display all splits. Is this what the OP means? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
[Kmymoney-devel] [Bug 274435] importing gnucash makes payee from comment instead of corresponding account
https://bugs.kde.org/show_bug.cgi?id=274435 --- Comment #5 from Tony B 2011-06-02 11:13:41 --- The following is an extract from the manual re GnuCash import: Payees KMyMoney prefers that all transactions have a Payee (a generic term that encompasses both payees and payers), and unlike GnuCash, a list of these payees is maintained. Payee names are generated by the importer from the GnuCash transaction's Description field. This has proved satisfactory for some time now, with the option to over-ride in some circumstances, as detailed in my previous post. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
Re: [Kmymoney-devel] Anyone good with SQL?
On Thu, 11 Aug 2011 20:15:43 + (GMT) Colin Wright wrote: > It looks like it could be really slow in a large data set. If this > is done a lot you'd want an index on kmmSplits(accountid, postDate) > (or kmmSplits(accountid, txType, postDate) if it does lots of > type-based searches and N is uncommon). Unfortunately, 'N' is the most common. The alternative is 'S' which is used only with template schedule transactions, not 'real' ones. There is already an index on AccountId + txType; you can use 'Tools/Generate database SQL' in KMM to see the schema. Please remember if you create indexes or views of your own not to name them beginning with the three characters 'kmm' which are reserved for 'official' tables, etc. -- Cheers, Tonyb ___ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
Re: [Kmymoney-devel] Advantages to saving file as database
On Sat, 29 Oct 2011 11:37:45 -0400 Randy Lutzinger wrote: > I know that we are also able to save the file as a database. Does > saving the file as a database offer any advantages over using the > standard file format? Does encryption still work when saved as a > database? The main advantage of the database format is that you could create different views into your data using a product such as LibreOffice. You can go further if you have any knowledge of the SQL language used with relational databases. There is currently no encryption of the database itself. What I do is dump the DB to a file and encrypt that, then delete the DB. When I next need it, I decrypt and reload. If you're going to use Mysql, there is a script available under kmymoney/contrib/mysqlcrypt.sh which you may find useful. -- Cheers, Tonyb ___ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
[Kmymoney-devel] [Bug 286503] MySQL error while importing large QIF file.
https://bugs.kde.org/show_bug.cgi?id=286503 Tony B changed: What|Removed |Added CC||tonyb.sf...@ntlworld.com --- Comment #1 from Tony B 2011-11-25 09:30:24 --- Sorry for the delay in replying, but I have been away. The critical message here would seem to be "MySQL server has gone away". The following is an excerpt from the MySQL reference manual explanation of this error: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The most common reason for the MySQL server has gone away error is that the server timed out and closed the connection. By default, the server closes the connection after eight hours if nothing has happened. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Given the length of time your run is taking, could this perhaps be the reason? I'm afraid I don't know enough about the QIF importer to tell. Perhaps one of the other developers could analyze the backtrace and see what's happening. There are a number of other possible causes of this error listed in the manual, but without further information (e.g. the MySQL logs for the period) it's not possible to be specific. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
Re: [Kmymoney-devel] Bug: SQLite storing Bi-weekly as weekly?
On Tue, 24 Jan 2012 16:54:32 -0500 Eric Bonney wrote: > In working on my project this afternoon I think I may see a bug? > Looking at my raw sqlite data I have schedules that have an > occurenceString of Every Other Week, but the occurrence column shows > 4. > > Now looking at the mymonyschedule.h file is looks like OCCUR_WEEKLY > is 4 and OCCUR_EVERYOTHERWEEK is supposed to be 8. Looking at the latest source code I have, the database module does not do any specific processing here. It just stores the values it receives from the MyMoneySchedule object 'get' methods. Perhaps this stores it as weekly with a multiplier of 2? -- Cheers, Tonyb ___ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
Re: [Kmymoney-devel] [kmymoney4] [Bug 314491] KMyMoney Gnucash Import Crash
Yes, I'm still alive. I'm sending this to the list since I seem to have lost my KDE bugzilla signon; lack of use I guess. Did the OP try running his file through the GnuCash Check and Repair facility; under the Actions menu IIRC. It sometime picks out problems like this. Otherwise, the only alternative is to try to reproduce the problem using your file, which of course has privacy issues. At one time, I developed a GnuCash anonymizer. As I recall, it could be created by compiling the GNC import module stand-alone with an optional compiler flag set; something like GNCANON I think. I used it successfully on my own old GNC files once, but never got round to providing a distribution of it. Keep up the good work, guys. -- Cheers, Tonyb ___ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
Re: [Kmymoney-devel] Comments about KMyMoney
On 01/06/13 11:06, Dave Anderson-ACB wrote: are simply no good invoicing programs available for Linuxand I think that I have probably tried them allthe few that there are have limited functionality, or can not handle a credit note, or advance deposit, or etcand/or are web or MySQL based and I don't have any interest in using a web or cloud based system, etc. MySQL does not need to be web or cloud based; you can install it on your local machine if you have the resources. -- Cheers, Tonyb ___ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
[kmymoney] [Bug 440745] New: Update EUR/BTC price online does not work
https://bugs.kde.org/show_bug.cgi?id=440745 Bug ID: 440745 Summary: Update EUR/BTC price online does not work Product: kmymoney Version: 5.1.2 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: t...@marshall.name Target Milestone: --- SUMMARY KMyMoney does not retrieve the correct value of EUR/BTC when updating for a single date (which uses fx-rate.net). STEPS TO REPRODUCE 1. Select the menu Tools => Update Stock and Currency Prices 2. Select the currency pair EUR > BTC 3. Click the button "Update Selected" OBSERVED RESULT Fetching URL https://fx-rate.net/EUR/BTC... Identifier found: 'EUR/BTC' Price found: '2.664' (2.664) Date found: 'Sun Aug 8 2021' Price for EUR > BTC updated (ID EUR BTC) EXPECTED RESULT Fetching URL https://fx-rate.net/EUR/BTC... Identifier found: 'EUR/BTC' Price found: '2.664e-5' (0.2664) Date found: 'Sun Aug 8 2021' Price for EUR > BTC updated (ID EUR BTC) SOFTWARE/OS VERSIONS Windows: Windows 10 Home 20H2 ADDITIONAL INFORMATION I am using KMyMoney version 5.1.2-772e77894. For EUR/BTC, fx-rate.net returns a number in scientific notation. The regex configuration that extracts this number is ([,\d+\.]+). I made a simple change to ([,\d+\.e-]+), then re-ran the STEPS TO REPRODUCE and KMyMoney displayed "Price found: '2.664e-5' (2.664e-05)" in the output. However, KMyMoney did not use this value to update the price history of the currency. Updating a range of prices also does not work (which uses stooq.com). I will submit a formal bug report if you want; however, it's easy to reproduce it. Fixing these bugs will allow the tracking of cryptocurrencies in KMyMoney and would be a very useful capability. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 465214] New: Add "Closed" flag to an account
https://bugs.kde.org/show_bug.cgi?id=465214 Bug ID: 465214 Summary: Add "Closed" flag to an account Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: t...@marshall.name Target Milestone: --- SUMMARY *** It would be nice to be able to mark an account as closed. Then, in the Reports filter, one closed accounts are by default excluded, unless one chooses to include them by clicking a a "Include closed accounts" checkbox. Microsoft Money used to have this feature and it was useful. I have over 25 years' of accounts in KMyMoney, and so I have accumulated a lot of closed accounts over time (due to moving country, banks etc.) *** -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 465214] Add "Closed" flag to an account
https://bugs.kde.org/show_bug.cgi?id=465214 --- Comment #2 from Tony --- "How hard did you look for this feature?" Obviously not hard enough. To be honest, it didn't occur to me that it'd be a menu option. I just assumed that it would be a status flag, just like "Preferred Account", that appeared in the Edit Account dialog window. IMO it's more suitable to make it a status field, but the important thing is that the ability exists to close the account. Thank you for replying. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 469195] New: Transaction report in native currency show wrong amount
https://bugs.kde.org/show_bug.cgi?id=469195 Bug ID: 469195 Summary: Transaction report in native currency show wrong amount Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-devel@kde.org Reporter: t...@marshall.name Target Milestone: --- Created attachment 158564 --> https://bugs.kde.org/attachment.cgi?id=158564&action=edit Three files described in the bug report. SUMMARY *** A transaction report showing a transfer from one account into an account having a different currency displays the amount and currency incorrectly when the "from" account is not included in the report. I do not want to include the "from" account in the report, as it includes too many transactions. I'm only interested in the transactions in the "to" account. *** STEPS TO REPRODUCE 1. Create a transaction that transfers from account "A" to account "B", which is in a different currency to "A". 2. Create a "Transactions by account" report and customise it to show only the transactions in account "B". 3. The line in the report that shows the amount transferred from account "A" has the currency of account "A" and the amount in the currency of account "B", but rounded using the decimal points defined for the currency of account "A". 4. Customise the report to include the transactions in account "A". 5. The line described in step 3 now displays correctly. SOFTWARE/OS VERSIONS Windows: ADDITIONAL INFORMATION Attached are 3 files: 1. CorrectReport.png shows the report with the correct amount and currency. However, for it to display correctly, I had to include the "transfer from" account in the report, which I don't want to do. 2. IncorrectReport.png shows the report with the incorrect amount and currency. 3. MyTest.kmy shows the problem. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 469195] Transaction report in native currency show wrong amount
https://bugs.kde.org/show_bug.cgi?id=469195 --- Comment #1 from Tony --- Created attachment 158565 --> https://bugs.kde.org/attachment.cgi?id=158565&action=edit Correct numbers -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 469195] Transaction report in native currency show wrong amount
https://bugs.kde.org/show_bug.cgi?id=469195 --- Comment #2 from Tony --- Created attachment 158566 --> https://bugs.kde.org/attachment.cgi?id=158566&action=edit Incorrect numbers -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 469195] Transaction report in native currency show wrong amount
https://bugs.kde.org/show_bug.cgi?id=469195 --- Comment #3 from Tony --- Created attachment 158567 --> https://bugs.kde.org/attachment.cgi?id=158567&action=edit Demonstration KMyMoney file -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 469195] Transaction report in native currency show wrong amount
https://bugs.kde.org/show_bug.cgi?id=469195 --- Comment #4 from Tony --- I submitted the but report with the compressed attachment. After that I realised I could upload the three files separately, which I did. However, I now see that I cannot delete the compressed attachment, so the files are uploaded twice. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 465214] Show open/closed status on Edit Account page, and allow changing it there
https://bugs.kde.org/show_bug.cgi?id=465214 --- Comment #5 from Tony --- I agree that it's not a bug. I reported it as such before learning that the feature was available on the Accounts menu. I would describe it as a feature request. I see no reason why one should not be able to edit a closed account, for example, to edit the name of the institution or the account number in case they were incorrect; or to change its status to "open" again. Curiously, I just received a bank statement from an account I thought was closed (by the bank in fact), so it seems natural to me to edit the account and change its status. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 491828] New: Currency settings show incorrect
https://bugs.kde.org/show_bug.cgi?id=491828 Bug ID: 491828 Summary: Currency settings show incorrect Classification: Applications Product: kmymoney Version: git (master) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: t...@marshall.name Target Milestone: --- Created attachment 172708 --> https://bugs.kde.org/attachment.cgi?id=172708&action=edit Screenshots of Bitcoin currency editors of v 5.1.3 and master SUMMARY Using KMyMoney 5.1 Version 5.1.3-eef0ff1, the Currency editor shows the Smallest account unit and Smallest cash unit of Bitcoin to be 0.0001. Using the master branch of KMyMoney (build 3407), the Currency editor shows £0.00 for these properties. Possibly as a result of this behaviour, the Transaction Report of transactions in an account whose currency is Bitcoin displays the amounts as BTC £0.02. KMyMoney 5.1 shows BTC 0.0176. The transaction editor also shows £0.02. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION Attached are screenshots of the Currency Editor from v 5.1.3 and master 3407. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 491828] Currency settings show incorrect
https://bugs.kde.org/show_bug.cgi?id=491828 Tony changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #13 from Tony --- I confirm that the Currency Editor and the Transaction Reports are fixed. The Balance field of the Ledger shows only two digits instead of eight for the Bitcoin account. I think it showed the £ symbol in front of it in the Windows 3407 build. (I just deleted it so I can't confirm it.) I'm unsure whether I should re-open this or submit a new ticket. If you prefer a new ticket I can create it. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 491828] Currency settings show incorrect
https://bugs.kde.org/show_bug.cgi?id=491828 --- Comment #15 from Tony --- There's another related problem when trying to enter into the Ledger a transfer from an EUR account to a BTC account. When entering the transaction into the EUR account, I can only enter a BTC amount of up to 2 decimal places, not 8 decimal places. And if I try to change the BTC amount in the BTC account, then the EUR amount changes. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 491828] Currency settings show incorrect
https://bugs.kde.org/show_bug.cgi?id=491828 --- Comment #18 from Tony --- (In reply to Ralf Habacker from comment #17) > (In reply to Ralf Habacker from comment #16) > > Monetary values will be formatted based on locale "de_DE" Example: > > "123,45 Ç" > > > > The used locale seems to be wrong. > > To be more precise: The locale used seems to be correct, but the currency > symbol does not match. The only information that KMyMoney would want from the OS's locale in order to format a money amount would be the thousands separator and decimal separator; the rest should come from the currency of the account, asset etc, or the base currency defined in KMyMoney. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 491828] Currency settings show incorrect
https://bugs.kde.org/show_bug.cgi?id=491828 --- Comment #21 from Tony --- I have just tried the latest build (3490) and the Balance column of the ledger continues to show the amount as, e.g. 0.16 instead of 0.16688250 (the 8 decimal places configured for the BTC currency) -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 501998] New: Warning is displayed when saving the KMyMoney file after entering a transaction for a new investment
https://bugs.kde.org/show_bug.cgi?id=501998 Bug ID: 501998 Summary: Warning is displayed when saving the KMyMoney file after entering a transaction for a new investment Classification: Applications Product: kmymoney Version: git (master) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-devel@kde.org Reporter: t...@kiwitones.xyz Target Milestone: --- SUMMARY I created an investment of type Stock and added a transaction with transaction date before today (the day I created the investment). I entered a Buy transaction of the stock, then I saved the KMyMoney data file. KMyMoney displays the following message in a window. Note that it is not possible to modify the creation date of the investment in the UI, so the warning cannot be avoided. * Problems with transactions * Transaction 'T021695' post date '24/03/2025' is older than opening date '%4' of account '25/03/2025'. Account opening date updated. * Potential problem with securities/currencies * The security 'Rheinmetall' has no price set for the first use on '24/03/2025'. Price for the security has been extracted from transaction and added to price history. Finished: 2 problems corrected. 0 problems still present. STEPS TO REPRODUCE 1. Create the stock investment called Rheinmetall (in this case) 2. Enter a buy transaction with transaction date before today. 3. Save the file. OBSERVED RESULT The aforementioned warning, which is also incorrectly formatted. EXPECTED RESULT No warning. SOFTWARE/OS VERSIONS Windows 10 ADDITIONAL INFORMATION KMyMoney version 5.1.92-bfd5a63 (from the Help/About KMyMoney menu) KMyMoney master build 4183 -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 501997] When buying / selling shares for an investment, the value is rounded to two decimal places
https://bugs.kde.org/show_bug.cgi?id=501997 --- Comment #3 from Tony --- Your test file works correctly as you stated. I deleted the Buy transaction and the security and recreated them and this time it behaved correctly as well. I suppose this case can be closed. If it happens to me again I'll try to determine the steps that reproduce the behaviour. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 501997] New: When buying / selling shares for an investment, the value is rounded to two decimal places
https://bugs.kde.org/show_bug.cgi?id=501997 Bug ID: 501997 Summary: When buying / selling shares for an investment, the value is rounded to two decimal places Classification: Applications Product: kmymoney Version: git (master) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-devel@kde.org Reporter: t...@kiwitones.xyz Target Milestone: --- SUMMARY This bug is identical to that reported in bug report 403249. It appears to be a regression. STEPS TO REPRODUCE 1. Create a new security of type Stock having price precision of 4 and remainder of Round. 2. In the ledger, enter a Buy transaction of 70 shares and Price/share of 35.6550 OBSERVED RESULT The Price/share changes to 35.65. The Total amount shows 2495.50 EXPECTED RESULT The Price/share should show 35.655. The Total amount should show 2495.85. SOFTWARE/OS VERSIONS Windows 10 Ubuntu Linux (I reproduced it on both platforms) ADDITIONAL INFORMATION KMyMoney version 5.1.92-bfd5a63 (from the Help/About KMyMoney menu) KMyMoney build master 4183 -- You are receiving this mail because: You are the assignee for the bug.
Re: [kmymoney] [Bug 458884] Windows and Linux SQLite databases are not compatible
On 14/08/2023 19:05, Jack via KMyMoney-devel wrote: https://bugs.kde.org/show_bug.cgi?id=458884 --- Comment #4 from Jack --- Not sure how this got lost, but in your last response, I think you misunderstood. KMM does not bundle sqlite itself, and that is the version I was looking for, to see if it doesn't match the linux version. However, given that an unencrypted sqlite database can successfullly be passed between LInux and Windows, it is almost certain that the problem is that the two different versions of sqlcipher are using different encryption mechanisms, or at least different keys. I recently had a case where saving as an encrypted sqlite database on Linux, I could not even open it with sqlcipher from command line. I think we will need an sqlite/sqlcipher expert to help solve this. SQLite databases should be compatible. SQLcipher changed encryption between versions 3 and 4. See https://www.zetetic.net/sqlcipher/sqlcipher-api/ -- Cheers TonyB
