David C.
Trading accounts are not the same as lots. Different concept, different code.
Just a for instance: trading accounts are turned on by book; lots can be
enabled by account.
David T.
On July 27, 2022 3:33:37 AM GMT+03:00, David Carlson
wrote:
>I believe that you are witnessing first
Thank you, I will check it out
All the best,
Eric
From: john
Sent: Monday, July 25, 2022 11:07 AM
To: Eric Hammond
Cc: gnucash-user@gnucash.org
Subject: Re: [GNC] tutorials or examples for connecting/programming for GnuCash
data access
On Jul 25, 2022, at 9:30 AM, Eric Hammond
I forgot to address fixing the mess.
I think there are two ways to fix it. The easiest is to restore your last
backup from before turning on TA's.
The other, iirc, is to manually delete all those TA's.
On Tue, Jul 26, 2022, 7:24 PM wrote:
> Fred,
>
> Not early in the guide, but in the section
I believe that you are witnessing first hand why trading accounts are not
enabled by default, i.e. they create a royal mess in your trading history.
You might want to re-read the recent thread about evil trading accounts.
They may work ok for some users who's documentation goals align with the
Fred,
Not early in the guide, but in the section dealing with multiple currencies
https://www.gnucash.org/docs/v4/C/gnucash-guide/currency_trading_accts.html and
discussed on the wiki (https://wiki.gnucash.org/wiki/Trading_Accounts).
I don't think anyone has yet written anything about any
Over the past several months, I have been importing Quicken data into
GnuCash. There is about 6 years of data and lots of transactions. Besides
normal income and expenses, that data involved many different stocks and
many different currencies. Recently, I saw a reference to "Trading"
accounts.
If you mean the gnucash-x.x-setup.exe distributed as part of releases, it's
built on Windows in the MSYS2 environment using gcc. You're correct that the
Python bindings aren't included. That's also the case for the macOS GnuCash.app
and flatpak. The reason is that the bindings must be linked
Please remember to copy the list on all replies.
While providing a stable library for other applications to use is a long-term
goal we've still got a fair amount of work to do before we can support it.
Until then we make absolutely no API or ABI stability guarantees for the shared
libraries:
