Yes, I've seen that error when I attempt to delete the split from the account where it shows up.
However, this was in the scheduled transaction editor that I almost certainly made from the checkbook account... My scheduled transaction was a 4-way split: The amount coming out of the checking account, and three different expense accounts. I was trying to delete one of the expense account splits. I went ahead and let the transaction enter (after I was unable to delete the split) and had no trouble deleting the unneeded split from the checking account. On Fri, Nov 1, 2024 at 3:38 PM David Carlson <david.carlson....@gmail.com> wrote: > That same 'problem' arises when attempting to delete the 'anchor' split > line in a register window. I think the 'anchor' split line is always > defined as being associated with the current register, but if there is more > than one split line linked to that register, which split is the anchor? Is > this the case? Can the user 'jump' to the other account register and find > that account split is now the 'anchor'? > > If the 'anchor' split was somehow visually identified in the register view > there would be less mystery here. > > > > > > On Fri, Nov 1, 2024 at 3:23 PM Stephen M. Butler <kg...@arrl.net> wrote: > > > Are you going in via Actions --> Scheduled Transactions --> Scheduled > > Transaction Editor? > > > > I did with the Accounts Tab being the only one opened. Found a > > Scheduled Transaction with four lines (splits). Deleted one line with > > no errors. Cancelled. > > > > Opened up the Account Register corresponding to the line I was going to > > delete and went back into the Scheduled Transaction Editor and deleted > > that same line again. No Errors. Cancelled out as unable to duplicate > > on Ubuntu 24.04.1 LTS running GnC Build ID: git > > 5.9-57-g26e452bab7+(2024-10-27). > > > > Is there something special about that split? Has variables? If the > > above scenario isn't what your doing can you post the detail steps. I'm > > running with a cmake with -DCMAKE_BUILD_TYPE=Asan and > > -DCMAKE_BUILD_TYPE=Debug so I should be able to get a good stack dump if > > I can make it fail on Ubuntu. > > > > Stephen M Butler > > > > stephen.m.butle...@gmail.com > > kg...@arrl.net > > 253-350-0166 > > ------------------------------------------- > > GnuPG Fingerprint: 8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8 > > > > On 11/1/24 12:59, David H wrote: > > > Richard, > > > > > > I can confirm the same thing happens on Win 10 Gnucash 5.9 and if you > try > > > it more than once on more than one scheduled txn Gnucash will crash :-) > > I > > > think from memory I've handled this situation in the past by right > > clicking > > > on the modified txn in the actual register and scheduling it again as a > > new > > > scheduled txn without the offending split and deleting the original > > > scheduled txn. > > > > > > Cheers David H. > > > > > > On Sat, 2 Nov 2024 at 01:50, R Losey <rlo...@gmail.com> wrote: > > > > > >> I brought up the scheduled transaction editor, and attempted to delete > > one > > >> of entry of a multi-split transaction, and I received the error > message: > > >> "You cannot delete this split", stating that it was anchoring this > > >> transaction to the register... this was in a register - it was the > > >> transaction editor. > > >> > > >> I am running the current version 5.9 on an M1 iMac running 14.6.1. I > > >> suspect it may happen on other platforms; I'll probably try on > Windows a > > >> bit later today. > > >> > > >> As a temporary workaround, I have set the amount of that split entry > to > > >> zero, and when it gets triggered and entered, I just delete the > unneeded > > >> line from the register, and it deletes without any problems. > > >> > > >> -- > > >> _________________________________ > > >> Richard Losey > > >> rlo...@gmail.com > > >> Micah 6:8 > > >> _______________________________________________ > > >> 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. > > >> > > > _______________________________________________ > > > 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. > > > > _______________________________________________ > > 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. > > > > > -- > David Carlson > _______________________________________________ > 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. > -- _________________________________ Richard Losey rlo...@gmail.com Micah 6:8 _______________________________________________ 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.
