Why are there 2 "Amount" columns in reports now?
bambi.d
Quicken Windows Subscription Member ✭✭
Transaction Reports show 2 columns for Amount - first one is right justified and the second (furthest right on the page) is bold and left justified. If I customize the report, the list of Columns shows 2 Amount fields. If I uncheck either one, it fixes the report. If I Reset Columns, that will correct the list and only show 1 Amount field. But this will happen again every time I make a new transaction report.
0
Best Answer
-
I would start by clicking on Reset Columns. If you are using reports that you customized and saved in an earlier version of Quicken, you may need to re-create these reports, starting with one of the built-in reports.QWin Premier subscription0
Answers
-
You're apparently running a somewhat older version of QWin. That bug has been fixed in later versions.
Q user since February, 1990. DOS Version 4
Now running Quicken Windows Subscription, Business & Personal
Retired "Certified Information Systems Auditor" & Bank Audit VP-1 -
I am a Subscriber user of Quicken Home & Business (version R29.22). So it's not the version, but it could be the age of the files since I have been a user a long long time and they have been converted many times over the years.
It seems that I never clicked on the "Reset Columns" button before yesterday. That may have fixed the doubling of Amount fields. But now I have the Tax Item selected on every report. Is there a way to change the default to NOT select Tax Item column?? Why do I need this column if I am not doing a tax report??0 -
Running the latest version of QWin (R31.5) and this problem still exists in almost every standard report.0
-
I would start by clicking on Reset Columns. If you are using reports that you customized and saved in an earlier version of Quicken, you may need to re-create these reports, starting with one of the built-in reports.QWin Premier subscription0
-
Have been modifying all custom reports. All standard (built-in) reports are still in error with amount columns duplicated as described at the top of this thread.0
-
gmk3 said:Running the latest version of QWin (R31.5) and this problem still exists in almost every standard report.Signature:
This is my website: http://www.quicknperlwiz.com/0 -
@gmk3, did you try clicking on the gear to customize the reports then clicking the Reset Columns button at the bottom right of the Display tab?
Some standard reports, Banking Transaction for example, now include the Tax Item field and it is selected by default. If you don't want to see that field, you can de-select it on the Display customization tab.
I believe the Tax Item field was added due to user requests. I think it would be better if it defaulted to not selected, so that the standard reports look the same as they did before the change.QWin Premier subscription0 -
"Transaction" for one (left side under standard reports) - also on the register report from within the register display. Each time, it's necessary to customize the report, uncheck the second "amount" column and redisplay the report.0
-
@gmk3, you still have not said if you tried clicking on "Reset Columns". That should fix the second Amount column.QWin Premier subscription0
-
Well in that case I don't know what to tell you I'm using R31.6 and here is what I get for: Reports -> Banking -> Transactions
Have you tried the "Reset Columns" as suggested?
Because in the past I (along with others) did have the problem and just doing that fixed the problem, even for the standard reports.Signature:
This is my website: http://www.quicknperlwiz.com/0 -
The fix you recommended did seem to resolve issues with the standard report. However, at the same time, it screwed up every saved report, which now contains an unwanted tax item and *no* amount column. Another casualty of Quicken's change control processes.0
-
If you click on the gear to customize the saved reports, you should be able to select the columns you want. Don't forget to re-save the reports after making any changes.QWin Premier subscription0
-
Of course.0
This discussion has been closed.