>>>>I am sure this question has been asked many times. Sorry for repeating it.
>>>>
>>>>Do you use nchar types in your database if your application is only used in the English speaking world?
>>>>
>>>>TIA
>>>
>>>If you're sure you don't need to store unicode data, then char (or varchar) will be good enough.
>>
>>Thank you. I can't really think of any unicode data that the customer would want to store in the field. I just want to be sure that I won't have to deal with the conversion to nchar.
>
>Not that I can think of. As long as you're only using basic English alphabet in all your character data, you're good without a need for unicode.
I also looked up a sample SQL Server database that came with a book written by someone who is a regular in this forum. And in his tables he also only uses char (not nchar). So I guess I am good with that. Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
