>That means that I have to create all indexes using UPPER function or store all the data in the upper case. It seems to me that I am back to Foxpro 2.x ways and SET COLLATE is absolutely useless. And if need to go internationally I still won't get correct letter sequense unless I use UPPER indexes.
>
>Dmitriy

I think that you'll note that if SET COLLATE is GENERAL, it doesn't order the table in the way you might think. Values which are equal, say "a" and "A", don't appear in their ASCII code sequences, but rather in the order they were added to the table. However, a query ordering by the same field will place the fields in their proper order will produce this result. I don't think that you need the UPPER() function in any place other than the WHERE clause.

As I may have mentioned before, the documentation does not mention that the collation sequence will have any impact on the returned result set.