Quicken Transaction Report Crashes

I'm unable to find that path; can you clarify?

Do you start by clicking "Reports" in the Quicken menu row? Is your actual path, Reports > Banking > Transaction? If not, what is the exact path?

When I try Reports > Banking > Transaction in R57.16, I have no problem customizing the report before displaying it.

Have you turned on the Quicken Preference Reports & Graphs > Customize report/graph before creating?

What are your Preferences > Early Access options set to?

What account type were you trying to report on?

What report customizations did you successfully enter before Quicken aborted?

What was the last thing you did before Quicken aborted?

It does sound like you might have some corruption. Validate does not find all corruption, and does not fix all the corruption it does find.

Do not expect any response from Quicken when you "Report a problem". It's extremely rare for the developers to contact those who submit Quicken problem reports.

I hope you sent your Sanitized data file with the report.

So after a reboot (and there was some Windows maintenance that went on the laptop during the shutdown), it seems to be ok. So no worries.

But the one item you asked about navigation that I'll clarify is that I use the ICONS (with show icons and text clicked) on the toolbar. Not the REPORTS that is on the FILE/EDIT/VIEW/.... main dropdown one line above the toolbar.

One of them is 'REPORTS'. When you click (first click) on this, a panel appears and under the bar "QUICKEN STANDARD REPORTS" there is a selection "TRANSACTION" one can click (second click) on.

Yeah, indeed I was worried about corruption. Hopefully it was just a fluke before the reboot w/maintenance was applied earlier this morning.

Thanks John for the reply.

SEE ABOVE

I don't think it will matter, but I'd like clarify your process for producing the report.

When you customized the Toolbar and placed what you refer to as "REPORTS" icon on the Toolbar, did you select "Reports & Graph Center" from the available options in the left hand column?

That places an icon on the Toolbar labelled "Reports".

Clicking Reports displays 2 columns; the column on the left is called "Quicken Standard Reports". Clicking "Banking" in the "Quicken Standard Reports" column displays several choices; one of which is "Transaction".

In theory, selecting "Transaction" at that point should produce the exact same report you would get by clicking "Reports" in the Quicken Menu row, selecting "Banking", then selecting "Transaction".

And if you have the Quicken Preference, Reports & Graphs > "Customize report/graph before creating", then every report/graph will offer you the Customize dialog before displaying the report.

Sorry if you knew all that already, but I just want to be certain we're on the same page.

Since your problem occurred during the report Customize dialog and since the report itself had never been displayed when the problem occurred, I guessed that you might be experiencing one of the reported problems with the new Quicken "Early Access" options, as the current Early Access options pertain to report customization.

I don't think anyone currently knows what causes the Early Access problems, so I believe it is usually suggested that the user turn off those 2 Early Access options when they experience problems with reports.

If you should see the problem again, I suggest you use Help > Report a problem, to notify the Quicken developers. Send your sanitized data file and your log files, along with a thorough problem description.

RE/"...but I just want to be certain we're > on the same page." Yes, both figuratively and accurately!

I didn't know about the "EARLY ACCESS" options, but in any case, I have neither checked. Thanks for pointing that out.

I'm just going to chalk this up to a fluke in some maintenance mismatch until my reboot. It hasn't happened again since I initiated the shutdown/restart and found there was some Windows maintenance that needed to be applied on my PC.

Thanks for the dialog, and I learned about the Early Access > >> So after a reboot (and there was some Windows maintenance that went on