Net worth report not working if I include intervals

Geissem
Geissem Member
My Net Worth by year is no longer working. All the accounts show zero balances. If I remove the intervals, it shows the correct accounts for today's date only, but I want to see the history like I could before.

Answers

  • Bob_L
    Bob_L SuperUser ✭✭✭✭✭
    edited April 2021
    Works for me using R23.10.  What version are you using?  Are you running a saved report?  If so, try creating a new one.
    EDIT  my version is 32.10

    Quicken Business & Personal Subscription, Windows 11 Home

  • Geissem
    Geissem Member
    I'm using R32.10. I have a saved report that no longer works. This was a very useful report as I could track balances year-to-year. I've tried creating new reports but the only way I get correct balances is if I include only the current date, not past years. Any reports showing past years have zero balances for all accounts, and a net worth of about 4% of what it should be. I have followed all suggestions, such as checking "include unrealized gains" but I still get all zeros. Any help would be appreciated.
  • NotACPA
    NotACPA SuperUser ✭✭✭✭✭
    I just ran the Net Worth report, from the earliest date to present, with the Columns set to Year.
    There were a lot of zeroes in the report, but upon inspection, it became apparent that those were accounts that I didn't hold for the entire time period (say, a mortgage that I took out last November OR a 2nd residence that I bought a year ago) AND loans and other account that are since closed.
    I didn't see anything out of order.
    SO, have you tried Validating your Q data file?  FILE, File Operations, Validate and Repair ... being SURE to check "Validate File", "Rebuild Investing Lots' and "Correct Investing Price History" before you click OK.

    Q user since February, 1990. DOS Version 4
    Now running Quicken Windows Subscription, Business & Personal
    Retired "Certified Information Systems Auditor" & Bank Audit VP

  • Geissem
    Geissem Member
    Thank you! That seems to have fixed the problem!
This discussion has been closed.