Henry on 20 Mar, 2018 12:40 PM
Thank you for contacting us.
Would it be possible for you to share your version and build number, to do this, open Moneydance and select Help --> About Moneydance (or Moneydance --> About Moneydance on a Mac) where the version and build number will be displayed?
Also did you recently edit the security from avg cost (default) to lot match?
Switching to latest beta is a disaster. When I went to the security screen
for Amazon and clicked Edit Lots, I got a message that there were no stock
sales to be matched. I thought the edit lots button would show me lot
history. I added a sale in the register, tried Edit Lots and had the same
I will go back to "official" version on the website, restore backup and
hope I can get back to work.
I am also unable to find this discussion in the MD help section.
Henry on 26 Mar, 2018 08:33 AM
Thank you for the errlog.txt, it looks like there are a multiple invalid transactions in the logs.
I've attached a file called "delete_invalid_txns.py" that should resolve this problem for you. Before proceeding, please back up your Moneydance data set, just in case something goes wrong. You can create a backup using the File --> Export Backup menu option.
To use the .py file, first save it to your computer and then follow these steps:
In Moneydance, select Window --> Python Scripting.
In the window that opens, select 'Open Script' then navigate to the .py file wherever you saved it on your system.
Select 'Run' to execute the file.
Wait a few moments until you see a message on screen, confirming the script has run successfully.
Once completed, restart Moneydance.
Sorry for slow response, personal problems got in the way.
I am going backward disastrously. I ran the provided .py file. The script
interface screen said 0 transactions deleted. When I restarted MD and hit
the Edit Lots button, I got the same message about no sales to match. I
tried to restore the backup I had made several times. At first I
accomplished nothing but getting MD to use 90% of CPU cycles for several
minutes at a time and create new MD files that I couldn't load. Finally I
succeeded in creating what looked like a successful restore. The banking
register had up-to-date info but the edit lots screen had the same message
about no sales to match. I tried a number of securities, including
securities imported from Quicken. All reported no sales to match and none
showed me existing lots.
Then the really scary part is I restored a backup I had made a few days ago
before messing with the py file, and had the same results, except the
banking transactions entered in the last few days are not in the register,
which obviously makes sense. Unless you can work some magic with the
errorlog (attached), it appears all lot info is lost.