I was obviously concerned about "lots" too. So I just hacked my xml file to delete the following slot from the account in question:
<slot:key>lot-mgmt</slot:key> Getting rid of that flag seems to be all that is needed to resolve my problem. Don't remember how I got it set in the first place, but it is evil. KB There may be an issue with your account structure. If you go to your > buy transaction(s) for that security, did you get the funds from the > brokerage account that is the 'parent' of the security account? If not, > you probably need to structure your account hierarchy (and your > transactions) similar to the description in the help manual. > > If that is not the problem, you may have found an instance of a bug that > I have seen a few times but have not been able to reliably reproduce. > Sometimes a transaction of this type seems to be out of balance and > um-editable. When I have seen this, I needed to change the transaction > number to something like the word 'Bad' then construct a new transaction > from scratch, being careful to avoid allowing gnucash to auto-enter any > part of the new transaction. Then I delete the 'Bad' transaction. I > think that once or twice I needed to actually build the new transaction > in a different account, then when it was close to being correct, change > the transaction to the correct account. I do suspect that the issue is > somehow related to the 'Lots' feature. I have studiously avoided that > feature since once trying it and finding something that I did not like. > Since then I have forgotten what it was that I didn't like. > > David C > > _______________________________________________ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
