Slow fill in Memorized Payee field

Don Neufeld

I am wondering if anyone else is experiencing this....when I fill in a name in the "Customer" field of an invoice, which draws from the Memorized Payee List, the appearance of each letter into the field is painfully...yes painfully....slow! I can type an entire name and the second letter finally arrives on screen. I realize this has to do with the search of the database, but in 2021 and with an apparently up to date app (downloaded yesterday) this is unacceptable. With only maybe a hundred names to search, this needs to be seamless. My previous 2016 version always had an annoying lag, but this is even slower. Any suggestions? Workaround? Setting changes? Can the programmers at Quicken please get on this!

Quicken Anja

Hello @Don Neufeld,

Thank you for reaching out to the Community and telling us about your issue, though I apologize that you are experiencing this.

To start with, if you haven't already, I suggest that you please try validating and/or super validating your data file. However, I do recommend that you first save a backup file first prior to performing these steps.

Validate: 

1. File
2. Validate and Repair File...
3. Validate File
   
4. Click OK
5. Close the Data Log
   
6. Close Quicken (leave it closed for at least 5 secs)
7. Reopen Quicken and see if the issue persists.

Super Validate:

1. File
2. Hold CTRL + Shift and click Validate and Repair File...
3. Super Validate File
4. Click OK
5. Close the Data Log
   
6. Close Quicken (leave it closed for at least 5 secs)
7. Reopen Quicken and see if the issue persists.

Let us know how it goes!

UKR

How many transactions do you have in your Customer Invoices (Accounts Receivables) account?

How many different Payees / Customers?

After several years of using the same account you may be hitting some design limits and it might be a good idea to add a 2nd Customer Invoices account for use with new invoices. Stop using the current (old) one.

Don Neufeld

I did the Validate and Super Validate functions and this has greatly improved the search rate. Still a slight lag but given the extent of the database, this is understandable and reasonable. Thanks for the directions for this fix!