The wrong pricing data is downloading for Vanguard Real Estate ETF (VNQ). How to fix?
xraysparrow
Quicken Windows Subscription Member
As of today 10/11/19 the wrong current and historical pricing data is being downloaded for Vanguard Real Estate ETF (VNQ). Is there a way to fix this?
Tagged:
0
Best Answer
-
Very strange. I set up VNQ in a test file and here is the result from the Security Detail view:
If you go to File > File Operations > Validate and Repair and select Correct investing price history and Repair, does that fix it? Back up your data file first in case something goes wrong.QWin Premier subscription5
Answers
-
I just tried it and it was very slow to add the security. It failed a couple of times but once it had been added to my watch list the current and historical prices appeared to be correct.QWin Premier subscription0
-
Hi Jim-
Thanks for your reply.
However, when I update historical prices all prices from earlier than one month ago are wrong- jumping from the low $90s to upwards of $213 and beyond. This is resulting in inaccurate performance data. When I try to delete some of the erroneous entries they repopulate upon redownloading historical price data. You are right- today’s quote is the correct one- those earlier than 9/11/19 are wrong.
Any other thoughts on how to fix?0 -
Very strange. I set up VNQ in a test file and here is the result from the Security Detail view:
If you go to File > File Operations > Validate and Repair and select Correct investing price history and Repair, does that fix it? Back up your data file first in case something goes wrong.QWin Premier subscription5 -
Another possibility is that you have two securities in Quicken both with the VNQ ticker but one of them is something with a different price.
For dates earlier than 30 days ago, the historical price download provides week or month end prices which might be getting mixed in with your other security.QWin Premier subscription0 -
I had to delete and rebuild, which fixed the erroneous VNQ data. Thanks for your help Jim!0
This discussion has been closed.