Cannot delete reminders in Bills and Income Reminders

sgtjdcusmc
sgtjdcusmc Member ✭✭

I tried all different ways. From Bills, from Tools etc. I still get:

Any suggestions?

Comments

  • Bob_L
    Bob_L Quicken Windows Subscription SuperUser ✭✭✭✭✭

    Could be that because it was one time only and is now done, you just need to close and reopen Quicken. Have you tried that?

    Quicken Business & Personal Subscription, Windows 11 Home

  • sgtjdcusmc
    sgtjdcusmc Member ✭✭

    Thank you. Yes, I use Quicken often I every time I try to delete those reminders.

  • QuickUserPSP
    QuickUserPSP Member, Windows Beta Beta

    @sgtjdcusmc - have you tried any of the Bill repair options in the Bills & Income tab?

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

    AFAIK, running Validate and Supervalidate both should make those "Done" reminders either disappear or make it possible to delete them from the Bills and Income Reminder dialog shown in the first image, using "Delete" from the Menu line.

    Validate and Supervalidate instructions
    First save a backup file prior to performing these steps
    Validate: 
    • Click File
    • Select Validate and Repair File...
    • Select Validate File
    • If the data file contains investment accounts also select "Rebuild investing lots".
    • If you suspect that a damaged Quotes Price History causes your problems, also select "Correct investing price history" functions "Delete" or "Repair and Rebuild".
    • Click OK
    • Review the Data Log. Anything interesting in there, worthwhile posting here?
    • Close Quicken (leave it closed for about 30 secs)
    • Reopen Quicken and see if the issue persists.

    Super Validate:
    • Click File
    • Press and hold both CTRL and Shift keys while you click Validate and Repair File...
    • Select Supervalidate File
    • Click OK
    • Review the Data Log. Anything interesting in there, worthwhile posting here?
    • Close Quicken (leave it closed for about 30 secs)
    • Reopen Quicken and see if the issue persists.

This discussion has been closed.