I'm not aware of any built in localization handling like that in SQL Server.I would suggest that you not just add a field to your table to hold the other value, but instead create a another table and link it to your existing table and include a CodePage/LocalID/CulterID (whatever you want to use) so that you can support any number of locals.For a rough example, something like:CREATE TABLE Fabric(ID INT, Description VARCHAR(255), FabricNameDefault NVARCHAR(255))CREATE TABLE FabricLocal(ID INT, CodePage INT, FabricNameLocal NVARCHAR(255))
With FabricLocal.ID being a foreign key to Fabric.ID.EDIT: Here is a link of a possible way to Localize text for your web app:[url]http://devpinoy.org/blogs/dehranph/archive/2006/11/08/l10n-localization-on-database.aspx[/url]-Ryan