Find/Replace from the Edit Menu Can Take an Hour to Render Results

Quicken's speed is not determined by its ability to query the data in the database but rather the processes used to render the data into a GUI form. This can be demonstrated by testing the speed at which data can be accessed in the Find/Edit window.

To reproduce the problem, use a Find, "Any Field", "Exact", "0.27". It will search the entire data base table almost instantly no matter how large the database is and render the few transactions, if any for 27 cents in a short period of time. You will notice the rendering takes orders of magnitude longer than the time to identify the query results (matched records shown in bottom right corner).

If you attempt a Find for a data set that returns several thousand matches you will see the number of matches almost instantly in the bottom right corner indicating it completed the query and has identified responsive transactions, but it may take an hour to render the visible results, during which time Quicken cannot be used to perform other functions.

The developers should fix the inefficient rendering methods used to assemble and display the query data. This same type of behavior is evident in Reports rendering and elsewhere within the product. Inefficient GUI rendering is the root cause of most of the complaints of Quicken being too slow.