[moneydance] Security amount field has different meaning for buy and sell in MD579/Mac OS 10.3.9

[Jeff DuMonthier]

After updating to 579 on my Mac (still running 10.3.9) I tried entering 
some security transactions and quickly became very confused.  In 
previous versions, the amount field in the register was always the base 
amount (not including fees) and there was no field showing the net 
amount.  Now when I enter a sell transaction starting with the number 
of shares, the base amount (which causes the security price to be 
calculated) and finally the fee, the amount field changes to show the 
net amount as adjusted by the fee.  Buy transactions, on the other 
hand, work the way they used to.  The amount field does not adjust for 
the fee.  It still shows the base amount and the net is not shown.  So 
the amount field has a different meaning depending on whether a 
transaction is a buy or a sell.  It applies to past transactions as 
well as new ones, so at least the meaning doesn't change in the middle 
of the register but it is still confusing.  In addition, my IRA account 
which was reconciled as recently as two months back now seems to be 
missing a few hundred dollars as far back as I care to look, so I'm 
wondering if this isn't simply a display issue and it's actually 
interpreting past entries in the data file differently than they were 
intended when written by the previous version.  Although two other 
security accounts still seem to be ok, so maybe it is something unique 
to that account or some transaction in it.  I guess the worst case is I 
have to enter a correction transaction and try not to worry...

I've also had a couple instances recently of being unable to match lots 
after selling a security because a buy didn't show up in the lot 
matching form.  The portfolio view does calculate correctly that there 
are no remaining shares, but I cannot match the sell to the buys 
because one of the buys just isn't there.  I entered all transactions 
manually, so it shouldn't be a CUSSIP issue.  One of them I was able to 
fix by going back and editing some of the transactions without actually 
changing anything.  Another I have been unable to fix even after 
deleting all transactions but the first buy and reentering them.  This 
is the kind of problem that caused me to abandon Quicken: security lot 
histories that would self corrupt and there was no way to fix them 
other than deleting all transactions in that security and starting 
over.

                       -Jeff DuMonthier