Hello,
Gnucash 4.11 Windows 10
Having struggled once again with the extremely unreliable aspects of the
Lots Manager, I am resigned to the fact that, while an admirable
endeavor in concept, the Lots Manager is more trouble than it is worth,
and leads to books that cannot be considered accurate over the long term.
For the worst of these, see
https://bugs.gnucash.org/show_bug.cgi?id=798583 regarding how the Lots
Manager will change RECONCILED GAINS TRANSACTIONS silently. A second
complaint I have is that if there is a Lot-generated gain transaction in
the register, deleting this gain transaction ALSO DELETES THE SALE
TRANSACTION. I can't imagine why this would be considered an appropriate
linkage to embed in the code, and there's nothing in the register to
indicate this linkage. I'm also not pleased that I have had frequent
crashes using the Lot Manager, to the extent that I have had to
reconcile the same accounts multiple times in a single day. That gets
old faster than I do.
Today, I'm hoping for two things:
First, I'd like to be able to determine which accounts in my books have
lots embedded in them, so that I can go through and remove the lots and
ensure that my books don't get corrupted YET AGAIN by this code. Any
ideas on how to expose (and root out and eliminate) these lots is welcome.
Second, I would like to find a way to disable the Lots manager entirely
for my books, so that I don't EVER make the mistaken assumption that the
Lot Manager is a tool I can use with confidence. I recognize that this
second ask is unlikely to be possible, but I am nevertheless curious to
know how complicated it might be to strip out the code altogether in my
own fork so that it doesn't cause me any more anguish.
David T.
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
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.
