You localise your UI (which you are doing). Your data stays in one language. I don't see why you'd want to try and localise customer data? You can of course format things like DOB, Phone Number etc differently, but the data is language agnostic.
On Wed, Oct 27, 2010 at 12:51 PM, Usman <[email protected]> wrote: > Dear all, > i am facing a problem with a client. i have developed a desktop > application which is a data driven application. my client's demand is > that he wants this software to be running in multiple languages. as i > have idea of dotnet globalization and localization and i am able to > convert all my application's labels with selected language. but the > problem is that what to do with database ? > > say my client has stored a customer record in English and later on he > opens up the application in Spanish language then how will he be able > to find that customer in Spanish language as well ? > > what i am anticipating is that i need to have multiple databases for > each of the language and user has to provide data to the system > multiple times. but i have assessed that this is quit annoying for a > user to enter a record multiple times and even if number of languages > increase later on then number of input for a single record also > increases. so i want to know that is there any way to deal with this > problem ? is there any shortcut to overcome it ? > > any help in this regard shall highly be appreciated. > thanks in advance > > Regards, > Usman Majeed
