Categories - Usage column

KentoC58
KentoC58 Quicken Windows Subscription Member

Earlier version I was using, like maybe 2010 version……can't remember…………….when you clicked on the category list, I believe it showed how many instances of each category was being using. You could quickly see if you had two similar categories and one was being used more than the other and you could then migrate the lesser used one and then delete it to clean it up. I'm not seeing that function in the current software.

Best Answer

  • Boatnmaniac
    Boatnmaniac Quicken Windows Subscription SuperUser ✭✭✭✭✭
    Answer ✓

    In the upper right corner or the Category List should be a Gear icon. Click on that, check the box for Usage and then click on Done.

    Quicken Classic Premier (US) Subscription: R59.10 on Windows 11

Answers

  • Boatnmaniac
    Boatnmaniac Quicken Windows Subscription SuperUser ✭✭✭✭✭
    Answer ✓

    In the upper right corner or the Category List should be a Gear icon. Click on that, check the box for Usage and then click on Done.

    Quicken Classic Premier (US) Subscription: R59.10 on Windows 11

  • KentoC58
    KentoC58 Quicken Windows Subscription Member

    Exactly what I was talking about. Thanks so much for the help.

  • UKR
    UKR Quicken Windows Subscription SuperUser ✭✭✭✭✭

    It appears to me that, as of a few release updates ago, the Usage column, once added to the view, does not persist across Quicken sessions and must be selected again if you need it..

    Can someone confirm?

  • Rocket J Squirrel
    Rocket J Squirrel Quicken Windows Subscription SuperUser ✭✭✭✭✭

    @UKR my Usage column persists in R50.14.

    Quicken user since version 2 for DOS, now using QWin Biz & Personal Subscription (US) on Win10 Pro.

  • J_Mike
    J_Mike Quicken Windows Subscription SuperUser ✭✭✭✭✭

    Usage seemed to persist in R50.8

    Justnow updated to R50.14 and Usage continued to display.

    QWin Dlx under Parallels & Win10/

    QWin & QMac (Deluxe) Subscription
    Quicken user since 1991

This discussion has been closed.