open to today

In my checking ledger, I have a lot of upcoming transactions automatically entered to help me keep ahead of bills. Every time I open the ledger, it takes me to the very latest transactions which are usually 30 days ahead of today and I have to scroll up to see current. Is there a way to set quick to open to TODAY and put a blank entry line there?

Best Answer

  • Rocket J Squirrel
    Rocket J Squirrel Quicken Windows Subscription SuperUser ✭✭✭✭✭
    Answer ✓
    If you're willing to expend 3 keystrokes, CTRL-G, Enter, CTRL-I will go to today and open a blank transaction line.

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

Answers

  • Chris_QPW
    Chris_QPW Quicken Windows Subscription Member ✭✭✭✭
    No there isn't a way to do what you are requesting.

    I suggest that instead of actually entering the reminders ahead of time, I suggest that you just have the reminders show in the some period like 30 days ahead.

    Signature:
    This is my website: http://www.quicknperlwiz.com/
  • Chris_QPW
    Chris_QPW Quicken Windows Subscription Member ✭✭✭✭
    Actually I take that back, this won't solve your problem since you will still see all those transactions before the blank line for entering the transactions.  But a workaround would be to change the above setting back and forth as needed to see bills coming for different periods of time, and for easier entering (with "Don't show").  Which is possible if they aren't pre-entered way in the future.
    Signature:
    This is my website: http://www.quicknperlwiz.com/
  • Rocket J Squirrel
    Rocket J Squirrel Quicken Windows Subscription SuperUser ✭✭✭✭✭
    Answer ✓
    If you're willing to expend 3 keystrokes, CTRL-G, Enter, CTRL-I will go to today and open a blank transaction line.

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

  • Ben Willey
    Ben Willey Member ✭✭
    Thanks for the keystoke suggestions. That seems to be a good workaround
This discussion has been closed.