>Hi.
>I have index on char binary fields in two tables which i link with relation. The relation works only with the code page under which the index was created. So NOCPCONVERT is neglected when an index is created. This seems illogical... to me at least.
>(VFP 8.0)

Ever since FPD2.6, when codepages and collating sequences were introduced, it remained as it was then: for indexing on anything binary, Set Collate "Machine". Any other collating sequence will create trouble, because it maps characters and character combinations into byte pairs, so you never really know what maps into what, and the mapping isn't one-to-one. Other collating sequences map the uppercase and lowercase characters into same pairs, which makes different strings look the same when mapped.

So if your binary tag has any other collating sequence but Machine, you simply can't use it as a target in a relation. Just drop that tag and re-create it in Machine sequence.