Are any of the other devices a computer if so, did you upgrade that to 2019.
As you are syncing did your reset syncing? Disconnect mobile devices and set to don’t sync on computers, delete “.moneydancesync” folder in Dropbox and start syncing from scratch?
I am now running MD on only one computer. I have deleted all the sync files. I have replaced the data file with one from 30 December, Which I think predates MD 2019. The currencies are still haywire. So I think either currencies are held in another file or MD 2019 has a bug.
Remember I can’t see what you are seeing. One of my first question was “Can you explain further what you see when you state “The base currency (GBP) has gone haywire. It is never 1 and keeps changing.” Where do you see the 1 being another value?””
I am running 2019.0(1847) with base currency GBP, so not sure the is a bug in that build itself.
To determine this can you set up a test data set. FILE – NEW set up one bank account with a few transactions and see what happens.
But first close Moneydance then open it again. Wait for problem to occur then under HELP – CONSOLE WINDOW click COPY TO CLIPBOARD, close Moneydance. Open a text editor such as notepad and paste the error log into it. Save the text file and attach it to a post.
I tried that and various other things. It doesn't help; it doesn't show the base currency on the summary page and the data is not complicated enough to reproduce an error. I have tried going back to an earlier version of the application, the data and the application support (I am running on a mac). Nothing helps. I haven't managed to get back to Moneydance 2017 but I think I might have to.
I attach a screen shot of the relevant part of the summary page.
Your attachment indicates that you have somehow no base currency set or your base currency is not British Pounds or you have two British Pounds set up under TOOL – CURRENCY. I have reposted the screen shot from my post 1 with the base currency highlighted. Recheck. Post a screen shot equivalent to mine.
Last suggestions whilst you wait.
Make sure you have a backup
Uninstall 2019. Uninstalling will not affect your data set or backups.
There is a configuration fill called config.dict rename it to config.dict_old This file holds all your preferences including your key so make sure you have a copy of your key.
When you start Moneydance config.dict will be created in its default form, see what happens now.
The British Pound should not be listed on the summary page along with other exchange rates.
Double click on British Pounds then EDIT. Take a screen shot.
If there are any dated Rates click CLEAR ALL. Change RATE value to 1.
Then whatever happens post the screen shot with your comments.
You can't edit it while it is the base currency. I did change base currency from USD in 2015 when we moved country so it does hold a history. I could go in and delete it by temporarily changing base currency, though I wouldn't want it ti change any past transactions.
The fact you changed the base currency back in 2015 could be the key to the problem.
If you have a EXPORT BACKUP you can always RESTORE FROM BACKUP. The data including the setting of the base currency is in the backup.
My first thought was:-
So change base currency to USD. Then edit British Pound If there are any dated Rates click CLEAR ALL. Change RATE value to 1. Change the base currency back to British Pounds. But on reflection changing back to GBP would probably not convert all the dollar values back to Pounds as the exchange rate has been change to 1.
Probably best to wait for Sean. Will pass the info on about the 2015 change of base currency.
I have reverted back to MD2017 and data now ship shape, I just had to correct two stock prices. Base Currency now not shown on summary page. I will not upgrade again until the issue has been addressed.
One thing Sean will probably ask for is a copy of the error log file errlog.txt as I requested in post 6.
First close Moneydance then open it again. Wait for problem to occur then under HELP – CONSOLE WINDOW click COPY TO CLIPBOARD, close Moneydance. Open a text editor such as notepad and paste the error log into it. Save the text file and attach it to a post.
Edit post crossed, probably to late to post error log?
Out of interest in 2017 I set up a new data set in USD. Added an exchange rate. Added a USD and GBP bank account. Entered a transaction in each. Changed the base currency to GBP. EXPORT BACKUP. RESTORED FROM BACKUP in 2019 hoping to duplicate your problem, but no everything worked correctly.