> Regarding the added uppercased column, do you think
> that there could be any inconvenience using case-insensitive
> collation drivers instead of the added column? On the end
> there is one less column in the table
> to deal with.

It depends.
If sorting is the only issue you could also use a different collation
driver, but this does not ensure uniqueness regardless of caption on
primary keys.

So we tend to use nearly allways a seperate column. There is nothing
you have to deal with. Simply write a trigger which fills the
additional column and you are done.

Regards,
Frank.