lsr broken too

NOT a DB limitation : update via SQL maganement studio is OK

Update via Admin Data entry : it's OK

The only difference between online and data edit seems PDO usage ?

Isn't the replacement with ? indented by the administrator of the system?

PDO::SQLSRV_ENCODING_SYSTEM Data is 8-bit characters as specified in the code page of the Windows locale that is set on the system. Any multi-byte characters or characters that do not map into this code page are substituted with a single-byte question mark (?) character.
https://docs.microsoft.com/en-us/sql/connect/php/constants-microsoft-drivers-for-php-for-sql-server?view=sql-server-ver15

If there is a issue (LS;PHP,Windows), you might first check what kind of SQLDriver for PHP is installed.
https://docs.microsoft.com/en-us/sql/connect/php/download-drivers-php-sql-server?view=sql-server-ver15

Isn't the replacement with ? indented by the administrator of the system?

?

Update via

1. Limesurvey Admin Data entry : it's OK
2. Limesurvey online survey : it's KO

:)

I see. That would limit it to a certain SQL query inside LimeSurvey. If it only occurs answering a survey and retrieving answers on the next page. Tricky.

No,

Not retrevieng answer : retrievening is done via $_SESSION

UPDATE lime_survey_799727 SET [lastpage]=1, [799727X1290X16208]=' Просим Вас обосновать свои ответы и (или) проиллюстрировать их примерами: ' WHERE ID=1 : ?????? is saved
UPDATE lime_survey_799727 SET [lastpage]=:lastpage, [799727X1290X16208]= :param WHERE ID=1 with [ … Вас обосновать свои ответы и (или) проиллюстрировать их примерами is saved :)

I check : Move from
Yii::app()->db->createCommand($query)->query();
to
Response::model($this->sid)->findByPk($_SESSION[$this->sessid]['srid'])->update();
fix the issue

(bu i need less update on this commit)

Seems the 5.3, i check with 5.5

Moving to sqlsrv 5.6+ didn't fix the issue

https://github.com/LimeSurvey/LimeSurvey/pull/1353

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=29289

Thanks :)

Fixed in Release 3.21.3+191219