You said the work around is to delete and re-add, but does the re-add not
generate the same error? Is this only when editing a previously defined SX?
I’ll admit I’ve only seen this error when actually trying to edit a real
transaction in one account register when I was already “in” the same
tra
Hi-
Using GC 3.1 on Mint 18.3.
I've come across something that seems like a bug, but I thought I would
check here first because I didn't see an open bug already.
Under Edit Scheduled Transaction, click Template Transaction, attempt to
edit a value in any field of the transaction then move focus
MySQL and postgre are the only formats that can be password protected. I
have been using MySQL for many years. It takes more disc space, but it's
more secure, backups are small, and is an excellent backed for reporting.
On Thu, May 17, 2018, 3:58 PM GWB wrote:
> I have used xml, postgresql, and
I'm using v3.1 and OFX import works on Windows10.
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane,
Back in 2013 I got this to work but then never really put it to regular use
and so I have no idea what changed. But if you figure out how to fix it,
please post back to here.
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
__
I have used xml, postgresql, and sqlite (which must default to sqlite3
on Ubuntu) with gnucash. sqlite3, as mentioned already, is a good
compromise between a database backend and simplicity of set up.
PostgreSQL is, probably, technically the best of the database backend
options for being robust, a
Alton
Thanks for that "ACH" alternative. It looks elegant. I'm going to give
it a try and see if the procedure is clearly understandable (to me, in
practice) and how easy it is to make the entries. I suspect that once
the first transaction has been fully completed, GC may help by
auto-filling the
When playing with it I noticed zero performance hit on High Sierra. But I also
have no performance lag with XML. Mileage may vary.
Regards,
Adrien
> On May 17, 2018, at 9:07 AM, John Ralls wrote:
>
> Should be since the SQL (including SQLite3) backend saves each change
> immediately so there
I forgot to mention, be sure you are using version 3.1 as that is the newest
supported version.
If so, you should probably file a bug report then.
Regards,
Adrien
p.s. - please remember to copy the list on all replies as others may benefit
from the exchange.
> On May 17, 2018, at 12:25 AM, Ad
Thanks to everyone for the helpful thread! This definitely helps answer
my questions about storage format.
On Thu, May 17, 2018 at 12:36:03AM -0500, Adrien Monteleone wrote:
> If all you want is the ability to run outside queries for custom reporting or
> data integration, then sqlite3 is probab
FYI: ofx and qfx are, as I understand, functionally equivalent. OFX is the
generic version, while QFX is Quicken's version of the same.
David T
On May 17, 2018, at 4:47 PM, Dennis Powless wrote:
Is qfx the only output/export you get from your bank? If you can try ofx
or try to do the ex
Love my GNUcash; been using a couple of years. Just installed v3.1 and now
getting an error in one of the reports when clicking on the numbers, which
previously allowed me to drill down for more detail. Now I get: Bad URL:
owner=c2b81305d2c55...etc., etc.)This report (Receivable Aging) alway
Should be since the SQL (including SQLite3) backend saves each change
immediately so there is no bulk saving. The initial “save as” operation might
be, but that’s a one-time hit.
Regards,
John Ralls
> On May 17, 2018, at 6:35 AM, Sébastien de Menten wrote:
>
> Is the SQLite storage format im
Is the SQLite storage format immune to the issue regarding "very long time
to save the XML format" some users are experiencing?
On Thu, May 17, 2018, 10:46 David T. via gnucash-user <
gnucash-user@gnucash.org> wrote:
> And, as I noted in January, the sql format does not get compressed, so the
> f
In Windows Release 3.0 the OFX import is broken.
Either wait for release 3.2 or downgrade to 2.6.21 or lower, but at least
2.6.17 to avoid other missing features.
David C
On Thu, May 17, 2018, 6:48 AM Dennis Powless wrote:
> Is qfx the only output/export you get from your bank? If you can tr
Is qfx the only output/export you get from your bank? If you can try ofx
or try to do the export again, change the parameters on the export ie dates.
Make sure you’re in the account you’re importing to, ie that register is open.
Dennis
Sent from my iPhone
> On May 16, 2018, at 4:18 PM
And, as I noted in January, the sql format does not get compressed, so the
files are much larger.
On Thu, May 17, 2018 at 10:37, Adrien
Monteleone wrote: Keith,
The SQL backends are having a few issues at the moment. It would be a good idea
to search the list here and also to look ove
17 matches
Mail list logo
