Weird "FIND" behavior - anyone else see this?

Jun 25, 2023 Last reply: 2 years ago 33 Replies

Yes, Took me some time to figure out exactly where the ALL TRANSACTIONS link was.

But all is well now, except for my original problem that John has provided a circumvention for.

btw, I did send in an official bug report as per John's pointer, so we'll see what happens if they address is officially in a future update.

FWIW:

I forgot to mention earlier that when I did my first test searching for "gif3ts" in the global search field, I too got lots of transactions none of which had the text I searched for. But, when I visually scanned the "found" transactions, I believe all of them had a "3" somewhere in their Amount field.

It appeared that Quicken ignored the alphabetic search characters and just searched for the digit 3 in the Amount field. The search did not "find" any transactions that had the number 3 in the Memo field, for example - though a few such transactions did exist.

Offhand, I can't think of any reason for a search algorithm to behave that way that intentionally.

Strange! So far, I haven't heard back from them about my submission.

Does one usually get some form of acknowledgement, or if it is truly a bug, you'll see the fix listed in the information about the update?

It would be nice if they at least let me know that they received the report, or perhaps I don't know where to look for those that are submitted and not processed or, as we used to say in my professional career, "WORKING AS CODED" (vs."WORKING AS DESIGNED").

You should not expect to hear anything back from Quicken. I believe the only time Quicken contacts those who "Report a problem" is when they need additional information. I think your problem will be evident to them without the need for further contact.

You "might" see something in the Quicken Community "Alerts" (if others report the problem and Quicken wants to acknowledge it), but I wouldn't count on that.

You can report the problem in the Community yourself, which might trigger others (particularly SuperUsers) to comment, which "might" then get an alert posted.

OK John, thanks. Well, with your assistance on using the ALL TRANSACTIONS work-around, it's not that big a deal for me now. I'll just sit on this and wait.

My guess is that the presence of the digit triggers a separate search for an amount in addition to the text search. But that's just a guess. I can't see anything in the documentation that clarifies this. Bottom line is probably to refrain from mixing alpha and digits in a single search while reporting this to Quicken.

Boy, this is strange. I'm in my primary banking register.

In the FIND dialog box on the upper right, I enter "gifts" and I see about 40 transactions containing that string returned....so far, so good.

But if I enter "gif3ts" (with that "3" digit in the middle), I get

*thousands* of transactions returned, and I assure you, NONE of them have that string in any field. WTF??

I'm on Q 27.1.50.14 on Win 11. I've also verified this behavior also occurs on multiple QDF files and I've VALIDATED at least one of them to see if this fixes it.

I don't THINK a digit in the middle should be any sort of deliniator?

I did a cursory scan on the Q community to see if anyone else has reported this.

Anyone else see this issue?

I recently installed R51.10 on my laptop and retested this problem. [I'd say my testing was somewhere between cursory and thorough.]

It appears to me that part of the problem has been addressed.

A register search (including the "All Transactions" pseudo-register) finds all - and only - transactions with "gif3ts" in payee, or tag, or memo; including finding that text in split lines.

A global search also successfully finds the same transactions ... but it also still finds unqualified transactions (which all seem to have a "3" somewhere in their amount).

Yep, and that what was I first queried about. Still seems 'broke' to me too in that regard.

But since I do have the 'ALL TRANSACTIONS' option (even though I do have to toggle the date range to ALL DATES as a separate step), I am not as concerned about the lack of ability to do what I originally wanted.

Thanks for the update.

Odd. My All Transactions pseudo-register always defaults to "All Dates".

Hey John -

My transactions start in December 1997 some 26 years ago. And in total, I have over 13,500 individual transactions spread across some 50 separate Quicken accounts.

Maybe the bulk of those numbers triggers just 'LAST 12 MONTHS' in the filter?

I just set the filter to ALL DATES and exited and re-entered Quicken seeing if that was going to 'stick', but no joy. Came back as LAST 12 MONTHS.

Or perhaps there's a setting I don't know about?

How about the Quicken register Preference "Remember register filters after Quicken closes".

[Which negates my statement that "All Dates" is the "default" for the All Transactions register. Apparently, unlike other registers, the All Transactions register to defaults to Last 12 months. I just happen to have set my All Transactions register date filter to "All Dates" some time ago ... after I had told Quicken to remember that filter after Quicken closes. I sort of forgot about the Preference for remembering register filters and assumed I was seeing the default.]

"Remember register filters after Quicken closes".

FWIW: I haven't done exhaustive testing, but I think you can tell when a given register's filters are all set at their defaults by noting whether the green Reset button is present on the filter row. If you see that Reset button, I think you can assume at least one filter is not set to its default.

Hey, great! That does seem to work, and thanks!

Now I need to keep that set to ALL DATES and see if in the future when I am using other filters it doesn't impede other views which I would prefer to NOT be kept over a restart. But I can't off the top of my head think of any of those so this might indeed be a keeper.

I didn't known that option existed and thanks for pointing it out.

I keep telling you, you need to write a TIPS AND HINTS book sometime about Q!

This problem is still present in the latest release 52.28.

I use CTRL-F to do a global search all the time. I wasn't even aware of the all-accounts pseudo register (thanks, John Pollard).

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required