SET LANGUAGE TO xxxx,
All are useful and adequate functions / commands, no doubt.
But sometime inefficient for me; and, I’m using my own case convert function
By changing two national character set layout, usable for all languages.
Some (including mine) language include accented characters and in PC everything likes for English ! All non-english character come after “z” ! Damn !
Fortunately (many thanks to builders of Clipper), dBase indexes have opportunity of based (none only field content), any valid expression, including a return value of a function
So we can use a function for product correct value for correct indexing.