Thanks everyone: I think David's tab trick worked. It appears to have
worked anyways.
Now my next trick, is a double trick:
During the ownership of a company, it has changed it's name/code. How does
one best handle this?
and
I have 163 shares in a company that had a capital reconstruction, and a
Hi Derek,
Thank you for your explanation. I've given this further thought overnight and,
although I understand your thinking, your analogy has helped me see where
confusion might have arisen.
When you say "split the wood in two" you are using split(v), not
split(n).Calling each piece of the res
> On 22 Mar 2019, at 19:33, aeg via gnucash-user
> wrote:
--
I agree with Michael's points.A simple transaction consists of just one split
but two parts, and saying (pretending) that a simple transaction has two splits
is misleading.
I see no problems with the use
I'll throw some more confusion I'm afraid. I'd think a Split is somewhat
unique to GnuCash, for better or for worse. I don't think there's an
equivalent word in general usage. If we define Split as a "that which links
Transactions to Accounts" then there's no confusion here.
Technically a Transact
> On 22 Mar 2019, at 19:33, aeg via gnucash-user
> wrote:
--
I agree with Michael's points.A simple transaction consists of just one split
but two parts, and saying (pretending) that a simple transaction has two splits
is misleading.
I see no problems with the use
I managed to sort the capital reconstruction out: Stock split with a
negative value.
As for the naming and code issue: I think I'll just rename the stock to
it's final name, and enter notes on the earlier transactions before the
name change?
Or is there a proper way to handle this? I was also thin
I think this dispute has more to do with how we begin to learn about
transactions in double entry bookkeeping and that gnucash (and yes, most
equivalent "direct entry into the ledger" alternatives) begins with a
SIMPLIFIED entry that makes it quick/easy to enter the overwhelming
majority of tra
I'm sorry for the contrary provisions, but this is the most natural of what
should be simple transactions and split transactions:
See the figure:
[image: Single-Split Transaction.JPG]
Anything out of it only makes sense for non-accounting contexts and it's a
arm wrestling of professionals of diff
Forgive me, but this seems like much ado about nothing. For me the explanation
is simple. In every transaction there is a source account for the cash being
distributed and one or more destination accounts where the cash is distributed
to. It is proper to say when there is more than one destinati
Thank you to those who have tried to educate me on the use of the word "split"
in GnuCash, but whilst I believe that I understand how it is being used, the
reason for using such an ambiguous term remains puzzling when better
alternatives exist.
I have a piece of wood that has a split in it cause
On Sat, 23 Mar 2019 22:04:55 + (UTC)
aeg via gnucash-user wrote:
> Thank you to those who have tried to educate me on the use of the
> word "split" in GnuCash, but whilst I believe that I understand how
> it is being used, the reason for using such an ambiguous term remains
> puzzling when be
Thank you again for this helpful information.
I did have one other question about this. When I enter a split transaction
directly into GnuCash (by using the "Split" button), it allows me to give
each split of that transaction its own description. Since - if I understood
your explanation properly -
Michael et al,
I suspect that whether we use a term like entry or split, we will no doubt find
circumstances in which the usage can
become confusing or ambiguous. Entry can also mean a number of different things
depending upon the context. What is
perhaps more important is to define what is mean
Patrick,
When the Transaction is opened with the split button, the Description field
name should change to Memo. There are other
changes in the headings as described in the documentation (
https://www.gnucash.org/docs/v3/C/gnucash-help/trans-multi-enter.html). If my
understanding is correct, eac
14 matches
Mail list logo