What purpose is served by the Account Code field?

[David T.]

Dorel, 
That was not my thought at all; I use account codes as well. I sincerely doubt it would get removed. 
Ken's comments missed my point as well. I was noting some of the potential issues that his discovery underscored for me. That the tree view breaks down when the color column is leftmost is a design issue that developers might be interested in knowing. 
I'm not sure personally whether I will use color there or not (because I can have a narrower left column than if I use account code). I do find that a moderately deep hierarchy (7 levels) begins to strain my eye, and having the codes lined up is easier for me. But, we'll see. 
David

 
 
  On Sun, Feb 19, 2017 at 8:55, Dorel Ciornei via gnucash-user<gnucash-user at gnucash.org> wrote:   The Account Code is essential to me as I am using it to have a custom sorting order.So far the sorting is done correctly.
The code is just a numeric 5 digit number.
I hope no one gets the idea to remove it.Thank you all,Dorel

 

    On Saturday, February 18, 2017 9:37 PM, Ken Heard <kenslists at teksavvy.com> wrote:
 

 -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2017-02-19 00:42, David T. wrote:
> 
>> On Feb 18, 2017, at 5:57 PM, Ken Heard <kenslists at teksavvy.com>
>> wrote:
>> 
>> Since my original post I discovered that the left most column in
>> the accounts window -- whatever it may be -- is always a tree.
>> So if for example the placeholder column is placed there it will
>> be a tree, but the account name column will not be.
> 
> Interesting. I see what you describe. I wonder whether it was
> intended to have the first column be the locus of the tree
> structure; it is a little disconcerting to expand the account type,
> for example. Also, I note that if one puts the Account Color in
> this position, the tree display gets messed up, with the widgets
> being placed behind the data for the next column because the color
> column doesn’t resize. I’m not sure what alternative one would use,
> however.

For me the obvious solution would be not to use the colour option, a
needless complication causing more trouble than it is worth.

> Finally, it can be confusing if you have some accounts without
> codes, as it can be difficult to determine which portions of the
> tree are expanded, which aren’t, and where one part of the tree
> ends.

I have given all my accounts a both a code and a name in both the
Account Code and Account Name fields in the format "code: name".  So
the entries in both those fields are identical, although as I have
already said I see no purpose in the Account Code field.

(In order to use the colon as above I had to change in preferences the
accounts separator from colon to tilde.)

Regards, Ken


> David
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAlipEpUACgkQlNlJzOkJmTdESgCeKleR/PuVrRubZgbmDIHzXAD5
+/gAn0SB3YFIhsj3fZuTlva5g8xjvl42
=bXXS
-----END PGP SIGNATURE-----
_______________________________________________
gnucash-user mailing list
gnucash-user at gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

  
_______________________________________________
gnucash-user mailing list
gnucash-user at gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.