G
Guest
Hi,
I have read through the posts here and go through articles from MS, but
their solutions/workaround seems not satisfying.
Workarounds they suggested:
- To use StrComp() or ASC() functions
- To use other database or odbc driver that is case-sensitivity
- To use BINARY field
Currently I am using SELECT DISTINCT UNIX_LOGIN, ASC(USERNAME) ...
to avoid case sensitivity in my distinct. But it only works with the first
letter of UNIX_LOGIN field.
Anyone has better ideas to cope with this problem? I need alternatives since
I have to compare their performance.
Thanks a lot,
Pongthai
I have read through the posts here and go through articles from MS, but
their solutions/workaround seems not satisfying.
Workarounds they suggested:
- To use StrComp() or ASC() functions
- To use other database or odbc driver that is case-sensitivity
- To use BINARY field
Currently I am using SELECT DISTINCT UNIX_LOGIN, ASC(USERNAME) ...
to avoid case sensitivity in my distinct. But it only works with the first
letter of UNIX_LOGIN field.
Anyone has better ideas to cope with this problem? I need alternatives since
I have to compare their performance.
Thanks a lot,
Pongthai