Afternoon,

I need some help understanding this error when importing a tab delimited VV survey file.
I needed to add a question to a live survey so i followed the instructions here: Changing an active Survey

Got to the point of importing the file and I am getting:

CDbCommand failed to execute the SQL statement: SQLSTATE[22018]: [Microsoft][SQL Server Native Client 11.0][SQL Server]Conversion failed when converting the nvarchar value '17
' to data type int.. The SQL statement executed was: SELECT * FROM [dbo].[survey_843445] [t] WHERE [t].[id]=:yp0

Anyone had this issue and know a way of fixing it?

I have attached the VV file and column I is the new question.
Any help would be appreciated.

With the last version ?

If yes : can you provide a lss file and the vvimport.txt file in our bugtracker ?

Why don't you use VV2 version ?
Here you have a manual.limesurvey.org/Exporting_results#VV_version_1_TSV_file VV1 version file.

Hi Denis,

I am using Version 2.00
I did follow this manual when trying to export the results and then import but that's when i ran into the exception error

Hi,
It's the ' beginning the 17: i think excel adding this when you save the csv file. Maybe you can try with LibreOffice Calc .
The column style must be 'number' in excel.

Denis

Hi Denis,

I made sure the column was numerical and on import i'm getting a PHP Notice undefined index: lastpage.

I have attached the screenshot and import file, thanks for your help with this.

Hi,

VV import accept only TAB separated value.

Morning,

i have tried Libre Office Calc but you can't save as a .txt file in order for it to be tab separated.
I might have to resort to moving the responses across in the database tables, making sure they are mapped to the correct columns.

With LibreOffice calc : save as CSV and check "Edit filter settings": help.libreoffice.org/Calc/Importing_and_Exporting_CSV_Files
After rename the file

Thanks for your advice on this but it still didnt work.

Ended up moving the table across in the database pairing the columns up with the new columns.
Then imported the tokens table in the front end.

Hi,

I do it again yesterady in the last 2.05 without any problem.

Then : update, surely some fix in 2.05.

yeh must be something new in the new version, update is on the cards within the year.

Cheers for your help though