Dimitris,
The DataTable Locale property contains a CultureInfo that describes how
strings should be compared within the table. When you begin to localize your
application, one of the things you would probably want to do is to set the
Locale property to the current users locale when you create an instance of
the object.
Here is the relevant documentation:
http://msdn2.microsoft.com/en-us/library/system.data.datatable.locale(VS.71).aspx
--
Regards,
Bryan Porter
http://www.bryanporter.com/
"What A Horrible Night To Have A Curse!" - S. Belmont
"Dimitris Milonas" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hello,
>
> When I build a DataSet with the DataSet Designer (DataSet.xsd) every
> DataTable has the property "Locale" which is set (I guess) to the current
> collate of the table of the SQL Server (I'm using MSSQL). I want to build
> a web application which is language neutral or translated in two or more
> languages.
> Is this property of the DataTable in the Designer going to be a problem?
> If it is a problem, then how to overcome it?
> At the beginning, I wrote "I guess" because I really don't where this
> locale property came from? The MSSQL has collate sequence for "Latin1" for
> Western European languages but in the DataSet Designer the "locale"
> property of the DataTable doesn't have any value of "Latin1" instead it
> lists all the different countries and languages.
>
> Regards
> Dimitris Milonas
>
>
Similar Threads
