>>Ok, Cetin, I think you'll want to restate your position. Explain to me how M$ Word could include a helpful feature like skipping words in ALL CAPS when spell checking if it couldn't look at the data in a case sensitive fashion. No one else here has supported the statement you just made, so I'll make another assumption and assume that you misunderstood what I was saying or perhaps mistated what you were saying.
>
>MS Word is not a database application nor a language. It can even find formatted as arial 10 pt text.
>What I am saying I find it nonsense to have case-sensitivity in text fields unless I ask for it. If I need sensitivity or alike I can use binary/nocptrans or specify an option like CS.
>
>Can you even write my name in uppercase? Original lowercase is: çetin - I bet a virtual beer that you can't uppercase it correcly. Why I am saying this? Just to show in a computer language case-sensitivity is important in code but in database I have (should have) to choose it.
>
>Cetin

Then it's now safe to say that we agree that case-sensitivity is needed in data at times. I was talking about any data, of course, including database systems like VFP, SQL Server, etc. as well as M$ Word docs or PDF docs or whatever. You don't have to have it all the time, but it appears that your clarification shows that you do agree that it is necessary at times, which is all I was saying.

Perhaps we can end this thread if you agree to the below (or even if you don't):

CS in data . . . needed at times
CS in code . . . we agree to disagree

And then that would be that . . . we could move to important discussions like whether you should use . . .

# or <>

. . . <g>