Problems with Investment historical price chart accuracy

JeffC
JeffC Member ✭✭✭
edited December 2024 in Investing (Windows)

I have several examples like ATT below that are not showing the historical price correctly. This has be going on for a couple of months. As seen below, the current price is around 22 but the chart shows a base line around 17 with many random spikes. Is this a known issue and what can I do to correct it. thanks Jeff

image.png

Comments

  • q_lurker
    q_lurker Quicken Windows Subscription SuperUser ✭✭✭✭✭

    My 2-yr AT&T looks like

    image.png

    All those prices come from Quicken's third-party data supplier.

    My data is only below $15 from mid July, 2023 through Oct, 2023. Yours is below $15 for most of that time.

    My data didn't go over $20 until Sept, 2024. All your spikes are above $20.

    Your data appears to lack volume information and probably lacks Hi and Lo values. In that case, the data is from your brokerage and may reflect is mismatched security.

    AT&T's CUSIP is C00206R102. What shows in the that column of the Security List (Ctrl-Y) for your AT&T?

  • skeleton567
    skeleton567 Quicken Windows Other Member ✭✭✭✭
    edited November 2024

    JeffC, if you download prices, about all you can do at this point is go into your Holdings screen, right-click the security name, and select Price History. Find the time frame of the errors in the list and delete the invalid prices from the list. Check your security list and be sure you have the correct security data on the record. I don't know if Q allows you to have the same security identity on more than one security, but this could also lead to invalid pricing. Also be sure to back up your file and run the Validate and Repair function on it.

    I have maintained for some time that Quicken suffers from more than one file integrity problem. I believe that there are some serious design issues in the way they update, store, and retrieve our data. And I also believe that Quicken itself corrupts our data in some cases.

    I am currently working my way through a case where I tried to add or change some security symbols back in January 2024. Later I found that by following their recommended means of doing this my price history was similarly corrupted which drastically altered my data for gains and losses, causing variations of many thousands of dollars for transactions. I had to recover a backup file from January and am still manually re-entering all my data for 46 digital statements for all our investment accounts. This fiasco also required that I recreate all the data for my banking, credit card, and other statements which was also missing from the old backup.

    Then there is the issue that the Validate and Repair function makes unexplained modifications to some of our data without telling us what it is doing. I have had many situations where this function repeatedly makes incorrect assumptions and alters my data incorrectly, causing me to need to research and fix things it decides are incorrect.

    One of the scary things about Quicken is that I have read that they use a 'screen scrape' means of collecting your data. This is without a doubt a very mind-blowing thought for an old computer systems developer like myself. I also think I understand they require you to give their system your login in for your financial institutions in order to do this. This seems to me to extremely dangerous.

    Years ago I was involved in developing a system for a Fortune 500 corporation which collected data from a country-wide network of remote dealer servers. We actually provided the dealers with OUR software that collected and VALIDATED the data on their systems, reported errors TO THEM, and required the data to be valid before even sending it to our systems.

    I regularly read the discussions on this community and am appalled by the sheer number of failures of Quicken to collect valid data for their own software. This is precisely why I am still using Quicken 2014 Deluxe for Windows and have not upgraded, and NEVER download data. At least I can handle the issues that I experience.

    Ó¿Õ¬

    Faithful Q user since 1986, with historical data beginning in 1943, programmer, database designer and developer for 42 years, general troublemaker on Community.Quicken.Com
This discussion has been closed.