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

On 6/25/2023 3:18 PM, John Pollard wrote:
> On Sunday, June 25, 2023 at 9:47:48 AM UTC-5, Andrew wrote:
> 
>> MANY of my records
>> contain a digit inside other characters since they identify specific
>> people due to a professional identifier and this really sucks since I
>> can't use this to easily view those (and only those) transactions in the
>> register.
> 
> Can you be more specific about the construct you're using,
> in what transaction fields you use it (and why), and
> if, and why, you would need to see matching transactions from all possible accounts at one time,
> as opposed to searching just one account?

John, I'm not sure why any of what you ask is relevant to the issue as 
hand. What difference does WHY I use this got to do with the fact it 
doesn't work as described.  I'd prefer not to give the specific format 
for privacy purposes as to the actual client identifiers the 
organization uses.

I sure there are many times that the same string is in either the PAYEE 
or the COMMENT field and would want a search to return all the 
transactions.  It does so with 'gift', but not 'gif3t'.

So let's just say that one of the IDs is 'gif3t' (that was made up to 
start with), and it might be in the PAYEE field or in the COMMENT field 
of a transaction.   The search argument 'gift' shows correct returns as 
both my and Ken Blake see, but 'gif3t' (or any other term with a digit 
in it I think) doesn't match correctly.  Unless I am misunderstanding 
that the search argument does not allow alphanumerics which would be 
pretty useless in my case if so.


-- 
-----------------------------------------------------------
Regards -

- Andrew