Bret and Mark,
Thanks so much for the insights. At least now I can predict what my results will be, now that I know that in my environment [Q-S] means [QqRrS]. And I'm guessing that this isn't just a glitch in my old version, but it's behavior that will act the same way all the way through ASE 15.7 and probably beyond.
But, this really pisses me off. Not only because of the fact that the manual states that LIKE specifiers are case-sensitive. But I've been programming in Transact-SQL since ASE version 4.0 in 1990, and I thought I knew what I was doing. I like LIKE. I use it all the time. But I never had the faintest idea that this glitch existed. There's no telling how many software bugs I've created in my own code due to this. I mean, when I want to check whether a string contains at least one upper-case character, I naturally use %[A-Z]%. Isn't that what all of you would naturally use too? Well, now I know that's not guaranteed to work. At best, that is "non-portable code". I don't think I can ever use a range test in a LIKE again. It's as if Sybase said, "By the way, on the first Tuesday of each month, I will say 2+2=5."
- John.