I haven't investigated it in any real depth but I got a phonecall from a
customer reporting a very odd phenomenon.

Apparently when accented text is being used in one field, such as twice
"é" in this case, the locate on another just never finds a hit. Has this
been observed before...?

Dominic,

<< Apparently when accented text is being used in one field, such as twice
"é" in this case, the locate on another just never finds a hit. Has this
been observed before...?  >>

When you say "on another", do you mean "on another field" ?  If so, then I
doubt that this is the exact cause.  The two shouldn't have anything to do
with each other.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:
> When you say "on another", do you mean "on another field" ?

Yes.

> If so,
> then I doubt that this is the exact cause.  The two shouldn't have
> anything to do with each other.

I can't agree with you more, but that is what appears to have happened.
I was pulling my two remaining hairs out trying to find the cause why a
locate wasn't working while the record certainly existed. Their system
has been working flawlessly for years now, until I got this phonecall.

The only thing I saw in the afflicted record that was different with
other records was that one field (the name field) contained "é"
characters, while none of the other records had them. The locate,
however, was being carried out on an entirely different field inside the
record (also a string field).

I then proceeded to remove the "é" characters (I replaced them by "e"s)
and tried again. Bingo, it worked. Go figure!

OMG! Had time to look a bit deeper and noticed there was a filter active
in the background. This filter (event) assigned the following to the
filter string:

F := format('pos("%s" in upper(Name) >
0',[F,Uppercase(edCustomerName.Text)])

The Uppercase function turns "é" into "é", not into "É", which I suppose
DBISAM's Upper is doing?

This is one of those things...

Anyhow, nothing to do with DBISAM. All to do with the Uppercase
function! Load of my mind.

Thanks for bearing with me and cheers, (and sorry for scaring you)
Dom

Dominic Willems wrote:
> F := format('pos("%s" in upper(Name) >
> 0',[F,Uppercase(edCustomerName.Text)])

This should read

F := format('pos("%s" in upper(Name) >
0',[Uppercase(edCustomerName.Text)])

(had simplified the snippet for essence but had forgotten about that F)

Using AnsiUppercase now. That works.

Cheers,
Dom

Thanks for letting us all know!

/Matthew Jones/

Dominic,

<< The Uppercase function turns "é" into "é", not into "É", which I suppose
DBISAM's Upper is doing? >>

Correct.  The upper-casing is done according to the full ANSI character set,
not the lower 127 ASCII character set.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:
> Correct.  The upper-casing is done according to the full ANSI
> character set, not the lower 127 ASCII character set.

Which is as it should be. Thanks!