Problem With Current Assets

[Adrien Monteleone]

Wm,

I don’t think there is a bug. I think this is user error.

It was the same-name issue that caused my confusion on where in the tree I was when assigning the parent. I was accidentally trying to set the account as its own parent, which triggers the error message since that is an impossibility. Certainly, I have many accounts with duplicate names, though they lie in different places in the tree.

Since the OP never replied back, I don’t know if that was their issue or not. Anyhow, they solved the problem by restoring an earlier file and proceeding again.


Regards,
Adrien

> On Mar 1, 2018, at 5:25 PM, Wm via gnucash-user <gnucash-user at gnucash.org> wrote:
> 
> On 27/02/2018 19:59, Adrien Monteleone wrote:
>> Playing around, I managed to trigger the error message.
>> I selected an account and then clicked the edit button. I then tried to re-assign it to itself as the parent. Of course, this is impossible.
> 
> gnc actually does some well thought out movements if you delete an account instead of moving it, if you want to experiment you create a new account, delete the old one and see if it does what you expect.
> 
>> Not sure if that’s what happened in your case. And for me, I recall now naming did play a part. Because I had some accounts very similarly named and I wasn’t paying close enough attention to the tree, I was attempting to place an account under itself rather than a different account.
> 
> If you can repeat that it is probably worth while doing a bug file.
> 
> placing accounts with the same name in a tree works very well in gnc as a rule
> 
> -- 
> Wm
> 
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at 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, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.