Thanks for bringing this to our attention, I see it also. This behavior changed between VFP6 and VFP6 SP3, it works as you expect in versions prior to VFP6 SP3. I passed it up the line on your behalf.

Thanks!

>Hi,
>
>On Message #849127 i post a big bug, but i see no reaction.
>
>I replay the problem in simpler way.
>
>

>CLEAR
>Create Cursor test(F1 C(2))
>
>Index On F1  tag Num
>
>Insert into test(F1) values ('A ')
>Insert into test(F1) values ('A'+CHR(0))
>Insert into test(F1) values ('B'+CHR(0))
>
>? 'Found() = ', KEYMATCH('A'+CHR(0)),SEEK('A'+CHR(0)),INDEXSEEK('A'+CHR(0))
>
>REINDEX
>
>? 'Found() = ', KEYMATCH('A'+CHR(0)),SEEK('A'+CHR(0)),INDEXSEEK('A'+CHR(0))
>
>LOCATE FOR F1=='A'+CHR(0)
>? FOUND()
>SELECT * from ALIAS() WHERE F1=='A'+CHR(0)
>

>
>Then, when a string Index expression can end with CHR(0), VFP index is bad.
>
>On Message #849429 i put a workaround.
>
>Fabio