- Posts: 2
- Thank you received: 1
Welcome to the LimeSurvey Community Forum
Ask the community, share ideas, and connect with other LimeSurvey users!
multiple choice error when save Failed to convert nvarchar value
- viv50
- Topic Author
- Offline
- New Member
Less
More
2 months 3 weeks ago #257026
by viv50
multiple choice error when save Failed to convert nvarchar value was created by viv50
Please help us help you and fill where relevant:
Your LimeSurvey version: limesurvey6.4.3
Own server or LimeSurvey hosting:Own
Survey theme/template:
==================
Hello, I installed the community edition of Limesurvey and its database is SQL SERVER 2017. I have an error when validating the survey when I want to add a multiple-choice question of type M. CDbCommand was unable to execute the SQL command: SQLSTATE[22018]: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Failed to convert the nvarchar value 'new65038' into data type int. The SQL statement executed was: SELECT TOP 1 * FROM [dbo].[lime_questions] [t] WHERE [t].[qid]=:yp0 AND [t].[scale_id]=:yp1 AND [t].[sid]=:yp2 AND [t].[parent_qid]=:yp3. Bound with :yp0='new65038', :yp1=0, :yp2='496362', :yp3='1'
Can you help me ?
Kind Regards,
Vivien.
Your LimeSurvey version: limesurvey6.4.3
Own server or LimeSurvey hosting:Own
Survey theme/template:
==================
Hello, I installed the community edition of Limesurvey and its database is SQL SERVER 2017. I have an error when validating the survey when I want to add a multiple-choice question of type M. CDbCommand was unable to execute the SQL command: SQLSTATE[22018]: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Failed to convert the nvarchar value 'new65038' into data type int. The SQL statement executed was: SELECT TOP 1 * FROM [dbo].[lime_questions] [t] WHERE [t].[qid]=:yp0 AND [t].[scale_id]=:yp1 AND [t].[sid]=:yp2 AND [t].[parent_qid]=:yp3. Bound with :yp0='new65038', :yp1=0, :yp2='496362', :yp3='1'
Can you help me ?
Kind Regards,
Vivien.
Please Log in to join the conversation.
- holch
- Offline
- LimeSurvey Community Team
Less
More
- Posts: 11712
- Thank you received: 2756
2 months 3 weeks ago #257085
by holch
I answer at the LimeSurvey forum in my spare time, I'm not a LimeSurvey GmbH employee.
No support via private message.
Replied by holch on topic multiple choice error when save Failed to convert nvarchar value
Not directly a help, but the mainstream EOL of SQL Server 2017 was on Oct 11, 2022 (extended end date is Oct 12, 2027).
To your issue: Limesurvey is mainly developed on MySQL and thus not as extensively tested for MS SQL or Postgre.
I would create a bug report.
To your issue: Limesurvey is mainly developed on MySQL and thus not as extensively tested for MS SQL or Postgre.
I would create a bug report.
I answer at the LimeSurvey forum in my spare time, I'm not a LimeSurvey GmbH employee.
No support via private message.
Please Log in to join the conversation.
- DenisChenu
- Offline
- LimeSurvey Community Team
Less
More
- Posts: 13716
- Thank you received: 2502
2 months 3 weeks ago #257523
by DenisChenu
I think this issue was already fixed : start to update your version.
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member, professional service on demand , plugin development .
I don't answer to private message.
Replied by DenisChenu on topic multiple choice error when save Failed to convert nvarchar value
We have some power user on MSSQL nowI would create a bug report.
I think this issue was already fixed : start to update your version.
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member, professional service on demand , plugin development .
I don't answer to private message.
The following user(s) said Thank You: viv50
Please Log in to join the conversation.
- viv50
- Topic Author
- Offline
- New Member
Less
More
- Posts: 2
- Thank you received: 1
2 months 2 weeks ago #257894
by viv50
Replied by viv50 on topic multiple choice error when save Failed to convert nvarchar value
the last update ( 6.4.10 ) solved this bug
Thanks
Thanks
The following user(s) said Thank You: DenisChenu
Please Log in to join the conversation.