Re: Weird "FIND" behavior - anyone else see this?

On Monday, June 26, 2023 at 7:22:43 AM UTC-5, Andrew wrote:
> On 6/26/2023 1:25 AM, Taxed and Spent wrote: 
> > Wouldn't a transaction report do the trick, since this is obviously some 
> > sort of flaw?

> But the problem with that (which I tried) is that I don't see how you 
> can 'filter' that report to find an occurrence of a string in ALL fields 
> of a transaction. 
> 
> As an example, say you receive a monthly deposit from your daughter 
> "Joan". And then the next month in your comment field you write 
> something like "Joan overpaid last month". You might wish to see BOTH 
> of those transactions with the string "Joan" which I don't think you can 
> specify in a transaction report, thus the need to use the SEARCH BOX.

I realize your example may be too simple to represent what you really want to do, 
but to address just your example:
I believe you could use the report Customize "matching" feature to show those 
two transactions.  
On the report Customize > Payees tab, you could key "..joan.." in the "Payee contains" 
matching field, and "..joan.." in the "Memo contains" matching field.

[The double periods tell Quicken to accept any (or no) characters where the periods are. 
The potential issue for "matching" in reports is that when two fields are used for matching, 
their criteria are in an "AND" relationship: that is, both specified matching criteria must be 
satisfied. In the example; if "..joan.. only appeared in the payee field of a transaction, 
or only appeared in the memo field of a transaction, the transaction would not qualify. ]