Jason,

Which is why decent databases allow you to supply an extrnal collation
sequence... it makes it so easy to do this sort of thing.

Rik,

one advantage of Jason's suggestion is that UC equivalent can have silly
characters removed from it such as comma, dash, apostrophe, accent, space.
Then it doesnt matter if the user gets these wrong... you remove them from
his search criteria before applying.

----- Original Message -----
From: "Jason Wharton" <jwharton@...>
To: <IBObjects@yahoogroups.com>
Sent: Thursday, 5 April 2001 04:44
Subject: Re: [IBO] FW: Uppercase


> It probably has to do with the ORDER BY situation. It doesn't allow you to
> use the UPPER( ) function in the order by clause. You should maintain an
> uppercase equivalent column in your table and use it in the
ColumnAttributes
> NOCASE setting for this to work 100%.
>
> HTH,
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com
>
>
> ----- Original Message -----
> From: "Rik" <rik@...>
> To: <ibobjects@yahoogroups.com>
> Sent: Wednesday, April 04, 2001 5:21 AM
> Subject: [IBO] FW: Uppercase
>
>
> >
> >
> > -----Oorspronkelijk bericht-----
> > Van: Rik [mailto:rik@...]
> > Verzonden: dinsdag 27 maart 2001 8:28
> > Aan: 'ibobjects@yahoogroups.com'
> > Onderwerp: Uppercase
> >
> > Hello,
> >
> > My customer can enter upper and lowercase characters in a field. When I
> > order and search in that field IBO sorts this field : first the
uppercase
> > and then the lowercase and so he can't search right.
> > I flagged already the 'case insensitive' in the columnattributes.
> > What do I wrong ?
> >
> >
> > rik@...
>
>
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>