This question is locked. New answers and comments are not allowed.
Hi,
We have an MS SQL Server 2005 database, collation is Latin1_General_CI_AS. Up to now only latin characters have been persisted in the DB tables, but recently a requirement to also store strings in cyrillic charsets has come up.
When updating an nvarchar field with cyrillic characters from within SSMS it works as expected - cyrillic characters are properly persisted. When updating the same field through Data Access with cyrillic characters what ends up being stored in the DB is a string consisting of question marks - '???????'.
If I was to write an insert/update statement manually (without the ORM) I would use the N qualifier: i.e. INSERT INTO myTable (myNvarCharField) VALUES (N'Поиск').
We are using an ancient version of Data Access - 4.3.22.901. I realize this version is way out of date. Unfortunately, an update to a more recent version is not easily possible for several reasons.
I'd really appreciate your help on this problem. Can I use our Open Access version to persist cyrillic text? Is there a recommended workaround if not?
Thanks!
Martin
We have an MS SQL Server 2005 database, collation is Latin1_General_CI_AS. Up to now only latin characters have been persisted in the DB tables, but recently a requirement to also store strings in cyrillic charsets has come up.
When updating an nvarchar field with cyrillic characters from within SSMS it works as expected - cyrillic characters are properly persisted. When updating the same field through Data Access with cyrillic characters what ends up being stored in the DB is a string consisting of question marks - '???????'.
If I was to write an insert/update statement manually (without the ORM) I would use the N qualifier: i.e. INSERT INTO myTable (myNvarCharField) VALUES (N'Поиск').
We are using an ancient version of Data Access - 4.3.22.901. I realize this version is way out of date. Unfortunately, an update to a more recent version is not easily possible for several reasons.
I'd really appreciate your help on this problem. Can I use our Open Access version to persist cyrillic text? Is there a recommended workaround if not?
Thanks!
Martin