nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Report Payee Totals are Grossly Wrong

nc00ks0n

running r37.67. This report finds transactions by single category and subtotals them by payee. One payee has one entry for $171.00 but its subtotal is 20,358,458,343,853,916.48. Most of the time when the report runs quicken crashes. I have to play with the date range to create a report that does not crash.

Find more posts tagged with

Reports

Windows

Comments

JKQUESTIONS

I have also noticed that subtotals on the left hand bard sometimes do not update till you exit and restart quicken. this was broken in a patch at end of decemeber and then they patched it and now the bug seems to be back. Does anyone else notice the subtotals to be off until close and reopen quicken

UKR

nc00ks0n said:

running r37.67. This report finds transactions by single category and subtotals them by payee. One payee has one entry for $171.00 but its subtotal is 20,358,458,343,853,916.48. Most of the time when the report runs quicken crashes. I have to play with the date range to create a report that does not crash.

That seems to indicate a damaged data file. Please Validate and Supervalidate your data file.

Advanced Data File Troubleshooting to Correct Problems With Quicken for Windows

If you're trying to reuse a Saved Report, saved in an older version of Quicken, please try the "Reset Columns" button (under the Customize icon) or recreate the report from scratch and, once successful, save it again.

nc00ks0n

I worked with support and they gave me a ticket number and said the fix will be in two weeks (Reference ticket # 916321). I installed R38.29 and see the problem still exists. Can you check to see if the fix was supposed to be in R38.29?
BTW we validated and super validated and found no damage.
Also notice R38.29 is super slow to respond. Is that expected too?

UKR

Patience, please. The programmers don't drop everything they're doing, just for one customer's problem report which may well be related to data file damage. Validate and Supervalidate aren't snake-oil-cure-all fixes and can't resolve problems which they're unable to detect.

As I said before, I suspect that your data file was damaged in way that cannot currently be repaired. You need to try and locate the damaged transaction and delete, then reenter it. If you are working with a Saved Report, try to recreate the report from scratch and re-save it, replacing the old saved report.

If you can't find the damaged transaction, I'd try the following actions:

Download and install the latest Mondo Patch file from https://www.quicken.com/support/update-and-mondo-patch-20182019-release-quicken-windows-subscription-product to ensure your Quicken software is up to date and correctly installed.
Reboot Windows.
Try Quicken again
If nothing helps, try to restore your Quicken data file from an Automatic or Manual backup taken just prior to the problems first occurring. https://www.quicken.com/support/how-backup-or-restore-your-quicken-data

nc00ks0n

No file corruption. Problem fixed in R38.30. This ticket can be closed.