If you have any trouble finding your Home Library folder, open Finder and select Go>Go to Folder> and type in:
This should pull up your local Library folder.
Once you've found your config.dict file, close Moneydance and rename it (to something like config2.dict, for example), then open Moneydance again and it will appear as though you've just installed Moneydance for the first time, so you'll have to locate and open your data set again. After you have done so open Moneydance and test the reminder, if it works close Moneydance and rename the original config.dict file back to config.dict and open Moneydance again to restore your original settings.
Henry, This sounds fine but when one reverts to the original config.dict file one will have two files with the same name. I assume I have to delete the ’new’ config.dict file before renaming config2.dict back to config.dict. Please confirm.
Second, what is this process really doing ? It sounds like my data file would be modified by the process of opening the data file with a ‘new' config.dict file, and these changes are then carried forward when returning to the ‘old’ config.dict file. What are the dangers in doing all of this ? I cannot possibly risk my data.
Henry on 08 Dec, 2018 01:54 PM
As the original config.dict file is only renamed it stays in it's original for, all changes are reverted once you delete the newly created config.dict file and rename the original file.
Nothing is lost.
The main purpose of this is to reset the behavior of the window, by removing the setup of the reminders temporarily, which restores the original behavior, once restored the config file can be restored and the correct behavior stays.
I have reported the issue to the development team and was told that this type of issue will not be present in the future release of Moneydance due to a change in the bundled java.
It probably has nothing to do with the config file and is a Java bug. There are a lot of them that make using MD problematic. Windows open behind other windows. Sometimes the window close button refuses to close a window. The only solution is to quit and restart MD. A true native app would avoid most of this, but lose the "easy" cross platform capabilities.
HI, Back in December 2108 Henry told me that a newer version of MD would not have this problem. However I have just loaded 2019.2 and almost immediately I got a pop-up window that would not close until I closed MD. So when will this be really fixed ?
I am running 2019.2 1860 and am still finding that pop up windows don't close on occasions. I reported this when I was running 2017 and was told by Henry on December 8 2018 that this would be fixed in future release. Clearly it's not. When can I expect a fix for this please ?