Actually, no string is being fed to the Keysource field. The lookup table is
called CATEGORIE, there is only one field in the table, no index and that
field is also called CATEGORIE, the SQL is SELECT CATEGORIE FROM CATEGORIE,
if I run the query in IB_SQL, I do get all entries back, including
lave-vaisselle. The KeyLinks is defined as
CATEGORIE.CATEGORIE=STOCK.CATEGORIE, I am not at the computer which has the
table presently, but some of the entries are: accessoire, rouleau, balai,
lave-vaisselle, four etc... Now, when I drop the combo box, if I select
lave-vaisselle, which is there to be selected, the field of the Keysource is
not updated, if I make another selection like accessoire, the field gets the
good information from the lookup table. If you are confused with the french
words, I think that using english names like data-set and dataset would be
equivalent not in meaning but in the actions that are happening here. This
morning, and even though it is Saturday, I have to get in to work and I will
try what Jason has suggested.

BTW, the charset is ISO8859_1.

> It has to do with the priority given to the non-characters in the

sort-order defined for character sets used by different languages. For
example, a hyphen is a more significant character in English and French
orthographies than it is in German, for example, where compounded words
rarely have hyphens.

>
> However, I can't see what sort order and character sets have to do with

the problem described, which is TIB_LookupCombo feeding an altered string to
the Keysource. I think the problem might be more closely related to what is
being used as the keylinks of the lookup dataset. There ARE problems when
the list value in the lookup list is being matched as the KeyLink to the
Keysource column.

>
> I would want to run the SQL for the lookup dataset in IB_SQL and look at

what is being returned there. Also, since an atomic key isn't being used
for the linkage, I would be wondering whether the link is being corrupted by
a size or character type mismatch.

>
> regards,
> Helen
>
>
> All for Open and Open for All
> InterBase Developer Initiative � http://www.interbase2000.org
> _______________________________________________________
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>