Design Studio

Problem:

Description:

The Design Studio sometimes crashed when writing to a Rich Text file.

The presence of a percent sign followed by the letter "s" in the text of a data or information element would cause the Design Studio to crash when user attempted to build a paper questionnaire, ACASI application, Codebook, or Change History document. The program now works correctly when writing Rich Text files.

Saving a specifications file that hasn't been modified causes the file to be unreadable.

If a user opened a file created in an earlier version of QDS, made no changes to the file, and then selected File | Save, the program would display the following error message when the user attempted to reopen the file: "An error occurred while reading the variable dictionary". At this point, the user would not be able to recover the file. This problem has been fixed. Now, if the user performs a File | Save on an older file that hasn't been modified, the user can still re-open and use the file without any problem.

CAPI/ACASI/HAPI

Problem:

Description:

The program sometimes crashed when writing to a Rich Text file.

If a survey participant typed a response containing "% s" into a text type response element, and the control file generated a summary report, the program crashed at the end of the interview. The program now works correctly when writing Rich Text files.

The program sometimes created a corrupted data file when the name of the questionnaire was very long.

This problem only occurred when the name of the .QDS file that generated the control file was greater than 48 characters in length and the designer had turned on encryption. When viewed in the Warehouse Manager, the first response in the file appeared to be missing. The program has been fixed to work correctly with long questionnaire names.

Data Entry

Problem:

Description:

The program sometimes created a corrupted data file when the name of the questionnaire was very long.

This problem only occurred when the name of the .QDS file that generated the control file was greater than 48 characters in length and the designer had turned on encryption. When viewed in the Warehouse Manager, the first response in the file appeared to be missing. The program has been fixed to work correctly with long questionnaire names.

Warehouse Manager

Problem:

Description:

The program sometimes crashed when writing to a Rich Text file.

If an interview contained a variable with "% s" in the response field, the program would crash when user selected "Save selected interview as." The program now works correctly when writing Rich Text files.

The SPSS export function reported an error if the standard version contained a long value label.

If the standard version contained a variable with a value label longer than 128 characters, the program issued the following message, "Cannot create SPSS file for reason 2". The program has been fixed to work as it has in the past, truncating long value labels to 60 characters.

The SPSS export function was unable to write long variable labels to exported data set.

If the standard version contained a variable with a variable label longer than 128 characters, the export ran but the label showed up as blank in SPSS. This has been fixed to work as it has in the past, truncating long variable labels to 120 characters.

The SPSS export function was unable to write long text responses in Chinese, Japanese, or Korean to exported data set.

If a text response in a Chinese, Japanese, or Korean language survey was greater than 128 characters, the export ran but the response showed up as blank in SPSS. This has been fixed to work properly. The response will now be included in the SPSS output with its length truncated to around 128 characters.

The SAS export function was unable to write long text responses to exported data set.

If a text response in any language was greater than 512 characters, the export ran but the response showed up as all spaces in SAS. This has been fixed to include the response in the output, truncated to 200 characters.