Hi
In oracle there is a client side nls_lang setting to ensure the client is Unicode… how is this done in SQL Server? Please mention this for various clients - SQL Native CLient, OLE DB Driver, SQL Server Management Studio etc.
What should be the setting if just one of my tables has Unicode data and the rest have non-unicode data . What are the implications in terms of both on display and data input for both types of columns?
The only setting that SQL Server 'requires', is that the column be defined to accept UNICODE values -either Nchar(), Nvarchar(), Ntext(), or Nvarchar(max). Then it will accept and store any bit string passed by the client.|||
Ok...say I have a windows form application that has a text box that accepts characters...how do I set it to read
say "Chinese characters" as well as English characters and also ....When I click on a button say "SUBMIT" the data entered in text area get stored as unicode.
Also I have another windows form where if i click on a button I need the display of both Chinse as well as English charcters,
Chince charcaters I am talking here are Double Bytes.
|||That functionality comes from the language/culture settings for the application, and the code pages available to the OS.
You would most likely get the help you need by posting in one of the appropriate .NET Windows Forms forums.
No comments:
Post a Comment