"Eurofirms." wrote:

> I don't think that the problem is the codepage. If I enter the text directly
> to the Database through enterprise manager, the text is correctly saved. The
> problem appears when I try to update the text through ADO.NET, so I think the
> problem is in the ADO connection.
>
> Is there some parameter or procedure to define the language used in the
> connection?.
> If I debug the program, the string is correctly passed through all levels to
> the SQLCommand.ExecuteNonQuery() procedure, but I can’t debug at this point.
>
>
> "Cor Ligthert [MVP]" wrote:
>
> > At least needs all the systems the right codepage, it seems the clients have
> > them while the server has another one.
> >
> > http://www.microsoft.com/globaldev/reference/sbcs/1250.mspx
> >
> > from not so a small man
> >
> > Cor
> >
> >
> >
> > "Eurofirms." <Eurofirms@discussions.microsoft.com> schreef in bericht
> > news:35620153-63BB-48D2-85C6-8D969B14E770@microsoft.com...
> > >I have a table where there are translations of various strings into
> > >different
> > > languages. I need to load this strings and allow some users to modify and
> > > update the strings back into the table.
> > >
> > > When I load a text written in polish, the application loads the data
> > > correctly and the user see all the characters in polish, but when the
> > > application writes back the string into the database, a word like
> > > wysokosci
> > > is converted into wysokosci.
> > >
> > > I tried to change the culture of the thread that executes the update to
> > > pl-PL (Polish) but the bug remains. Is there some way I can tell ADO.NET
> > > to
> > > preserve the language of the string when updated to the table?
> > >
> >
> >