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.
> At least needs all the systems the right codepage, it seems the clients have
> them while the server has another one.
[quoted text clipped - 20 lines]
> > to
> > preserve the language of the string when updated to the table?
Milosz Skalecki [MCAD] - 29 Mar 2007 20:58 GMT
Uszanowanie ;-)
Run SQL Server Profiler and see what is being executed. It should help you
to identify on which side (ADO.NET or SQL collation problems) causes the
problem(more likely).
Hope this helps

Signature
Milosz
> 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
[quoted text clipped - 30 lines]
> > > to
> > > preserve the language of the string when updated to the table?