>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)
>All the best.
NOCPCONVERT is to avoid conversion of the codepage when you get the data itself, not for indexing. As Gregory mentions, it is the collating sequence that is important in the index; and I agree that for an index on binary data, "MACHINE" is the only collation sequence that makes sense.
You shouldn't need NOCPCONVERT on binary data; NOCPCONVERT was introduced before the character binary and memo binary field types, so that you could specify which fields would not be codepage-translated.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
