In2quest 4.5.

1
Troubleshooting Guide

For more information about SPSS MR software products or if you have any questions
regarding your shipment or account, please visit our WWW site at
http://www.spss.com/spssmr or contact one of the SPSS MR offices listed below. For
assistance in using SPSS MR products or for installation help for one of the supported
hardware environments, contact Technical Support at http://www.spss.com/spssmr/support
SPSS MR
Maygrove House
67 Maygrove Road
London NW6 2EG
England
Phone: +44 (0) 20 7644 6000
Fax: +44 (0) 20 7624 5297
Support via email:
support-uk@spssmr.spss.com

SPSS MR
Level 9
181 Miller Street
North Sydney NSW 2060
Australia
Phone: +61 (0) 2 9954 5660
Fax: +61 (0) 2 9954 5616

SPSS MR
Suite 125
100 Merchant Street
Cincinnati OH 45246
USA
Phone: +1 (513) 771 7111
Fax:
+1 (513) 771 2121

Support via email:

support-au@spssmr.spss.com

Support via email:

support-us@spssmr.spss.com

In2quest, In2form, In2project, In2view, In2comm, In2data, In2tab, In2spss and In2script are
registered trademarks of SPSS A/S Denmark for its proprietary computer software. No
material describing such software may be produced or distributed without the written
permission of the owners of the trademark and license rights in the software and the copyrights
in the published materials.
The SOFTWARE and documentation are provided with RESTRICTED RIGHTS. Use,
duplication, or disclosure by the Government is subject to restrictions as set forth in
subdivision (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at
52.227-7013. Manufacturer is:
SPSS A/S, Roejelskaer 11, DK-2840 Holte, Denmark.
Phone: (+45) 45 46 02 00 Fax: (+45) 45 46 02 22.
General notice: Other product names mentioned herein are used for identification purposes
only and may be trademarks of their respective companies.
Windows is a registered trademark of Microsoft Corporation.
Copyright 19922001 by SPSS A/S Denmark.
All rights reserved.
Printed in London, England.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in
any form or by any means, electronic, mechanical, photocopying, recording, or otherwise,
without the prior written permission of the publisher.

Contents
1 Introduction

2 Tips and Tricks

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
On Back Office Computers for CAT Interviewing . . . . . . . . . . . . 3
On the Interview Machines for a CATI environment . . . . . . . . . . 5
Uninstalling In2quest . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
In2form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Corrupted Project file . . . .
Out of String Memory error .
Paste Special . . . . . . . . .
Large Multimedia files . . . .
Reference to Loop iterations
OLE Automation Error . . . .

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.7
.8
.8
11
15
16

In2project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Releasing Projects with Large Multimedia Files . . . . .
Respondent Data Files . . . . . . . . . . . . . . . . . . . .
Using In2project in a CATI environment . . . . . . . . . .
CATI Reducing the Number of Log Records . . . . . .
CATI Deleted/Purged projects still appear in In2view .
CATI Released project does not appear in In2view . .
Corrupted i2c File . . . . . . . . . . . . . . . . . . . . . . .
Synchronizing In2project and In2data . . . . . . . . . . .
Synchronizing Times on Interviewer Machines . . . . .
Sending Messages to Interviewers . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

16
17
18
19
22
23
23
24
25
26

Illegal Quota Line String error message . . . . . . . . . . . . . . . . 27

In2comm & Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Using Communications Software with Call Waiting . . . . . . . . . 28
In2view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Unable to open project . . . . . . . . . . . . . . . . . . . . . . . . . 30
Overflow error message . . . . . . . . . . . . . . . . . . . . . . . . . 31
Unable to save respondent error message . . . . . . . . . . . . . . 31
In2data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Corrupted database . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Runtime error 51 message . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter

Introduction

The purpose of this Troubleshooting Guide is to highlight specific information

contained in the manuals and guides, and to provide information on certain known
problems that you may encounter.
The majority of the problems you may encounter in the In2quest suite of programs
are explained on screen, in the ReadMe file, or in the user manual. Always refer to
these resources first for a solution to your problem.
We try to keep this guide as up-to-date as possible and include additional
information as it becomes available.
For the most recent copy of this guide, see the following web site:
http://www.spssmr.co.uk/qttsw/I2Q/faq/index.htm

In addition to this Troubleshooting Guide, the following manuals and guides are
available for the In2quest suite of programs:
Installation Instructions (not included in the installation)
In2quest Users Manual (included with In2quest Professional includes the

information contained in the In2form Designer Users Manual)

In2form Users Manual (included with In2form Designer)
Scriptwriters Guide (included with In2quest Professional and In2form Designer)
In2view Users Manual (included with In2quest Professional)

Chapter 1

The manuals and guides included with the installation are provided in PDF format.
You can read them online using Acrobat Reader. You can also print copies of these
manuals and guides using Acrobat Reader.
If you do not have Acrobat Reader, you can install it from the Installation CD. You
can also download a free copy from the following web site:
http://www.adobe.com/prodindex/acrobat/readstep.html

In2quest is highly adaptable to your needs, and thus you can use it in a number of
ways. Because of this, only the most common ways of using the features are
documented in the manuals and guides. You are given both general instructions and
examples. In addition, there are a number of example routings for In2form in the
sample project Sample.i2q in the \\In2quest\Samples folder.

Chapter

Tips and Tricks

This chapter mainly highlights information contained in the In2quest Users Manual
and provides additional information that is helpful for unique situations.

Installation
On Back Office Computers for Computer Aided Telephone Interviewing
To install In2quest on a Local Area Network (LAN), to use a Computer Aided
Telephone Interviewing environment (CATI) for example, you must set up In2quest
on the back office computer (server) and then create the shortcuts on the interviewer
machines. Of course, you must have the user-rights to create directories on the server;
otherwise, In2quest will not install properly. To install In2quest on a server, the server
must be running Windows NT. The files may reside on a Novell Netware server.
Note. These instructions assume that the person setting up the installation for a CATI
environment has basic knowledge of network administration.

To set up the server

 Create the server drive (F:) on the on the server (project machine) must be a computer
running Windows NT.
 Create a folder (directory) named In2quest on the local drive of the project machine.

Chapter 2

 Share this folder so that it is visible on the server drive (F:).

 Install In2quest on the server. The server (project machine) must be a computer
running Windows NT. Remember to include the CATI license file.
 Open In2project.
 From the menu choose:
Options
Setup
 In the Setup dialog box, click the Miscellaneous tab.
 Change the location of the Release file to F:\Release
 Click OK to save the Setup.

Although the only required change to the Setup for CATI is that you change the
Release folder to F:\Release, you can also change the location of all of the other folder
and file locations on the Miscellaneous and Directories tabs to that of the F: drive on the
server. To do this:
 Re-open the Setup dialog box.
 Change the location of the folder and file locations on the Miscellaneous and Directories
tabs to that of the F: drive on the server as follows:

On the Directories tab:

Database - F:\In2proj.i2p
Projects - F:\Projects
Licence File - F:\In2proj.lic

On the Miscellaneous tab:

Temporary - F:\Temp
Import - F:\Import
Data Backup - F:\Backup
 Click OK to save the Setup.

Tips and Tricks

Directory Structure
Before you can create the shortcuts on the interviewer machines, you must create the
necessary directory structure. In2project does this automatically when you release a
project. To create the directory structure:
 Create a project with all the required machines assigned.
 Release the project.

Releasing a project causes In2project to create all the necessary folders and files for the
interview machines. In2project must create these files before you can create the
shortcuts on the interviewer machines.

On the Interview Machines for a CATI environment

For a CATI environment, you only need to have In2view installed on the server, not on
each individual interviewer machine. You can run In2view for each interviewer
machine with a shortcut.

To set up the interviewer machines

 Map the shared server drive (F:) on all the interview machines. It is very important that

the letter chosen for the mapped drive is the same as that on the server.
 Create a shortcut to In2view.exe on each interview machine and change the Shortcut

Target properties to:

F:\In2view.exe /inifile=F:\Release\Lan\1\In2view.ini
 Click Apply.
 To check that you have written the shortcut correctly, click Find Target. This should
open a window showing the shared F: drive with the In2view.exe file highlighted.
 Once you have checked that you have written the target correctly, close the window.
 Click OK.

Chapter 2

Note. The only character space in the Shortcut Target properties is the space between
F:\In2view.exe and /inifile.
Tip. A quick way to create the shortcut is to drag-and-drop the In2view.exe file from F:
directory in the interviewer machines Windows Explorer to the interviewer machines
desktop (be sure to select the file from the mapped drive, not through the Network
Neighborhood). You can then add the /inifile=F:\Release\Lan\1\In2view.ini statement to
the Shortcut Target properties.

In this shortcut:
F: represents the shared server drive on which you installed In2quest.
The folder \Release\Lan represent folders on the server drive. The number 1

represents the folder for interviewer machine ID number one. You would change
this number to 2 for the interviewer machine with ID number two, and so on. These
folders are automatically created by In2project when you release a project.
The In2view.ini file is used to run In2view. In2project automatically creates this file.
If you are unsure as to the folder names, check your directory structure using your

Windows Explorer.
The interviewers can start administering questionnaires as soon as you release a
project. For more information on Setup, Settings, and Machine Options see the
relevant sections in the user manual.
Warning. We highly recommend that you use the short names for your file directories
when specifying file locations and directories. For example, a Windows 95 or
Windows NT file directory named Program Files has the short name PROGRA~1. It is
this short name you should use.

Uninstalling In2quest
To remove the program files from your system, please use the Uninstall feature in
Windows. Deleting the In2quest directory or copying the program files from one
computer to another does not deal with all the files associated with In2quest. To
reinstall the program, use the Installation CD. If you receive the error message File
component not registered when you install In2form Designer, contact your local SPSS
MR Support Center for assistance.

Tips and Tricks

Warning. Uninstalling In2quest deletes your license file (In2proj.lic) in the In2quest
folder. If you plan to reinstall In2quest, you must make a backup copy of your current
In2project license file and save it in a separate folder before you re-install In2quest.
Once you have re-installed In2quest, you must then replace the installed In2proj.lic file
with the back-up copy. If you do not do this, you will revert to the default user license.

In2form
Corrupted Project file
When trying to open an In2form project file (an *.i2q file), In2form issues a message
saying that the file is corrupted. There are two solutions to this problem Repair the
file, or use the Backup file (note that a back up file only exists if you have selected the
Backup projects option on the General tab of the Options dialog box).

To Repair the file:

 From the menu choose:
File
Repair
 In the Repair project file dialog box, select the file from the list.
 Click OK.

In2form will now attempt to repair the file.

To use the Backup file:

 In your browser, change the file name extension of the backup file from *.bak to *.i2q.
 Open In2form.
 From the menu choose:
File
Open Project

Chapter 2

 In the Open Project dialog box, select the file you just renamed from the list.
 Click OK.

In2form will now open the backup copy of the file.

Out of String Memory error

In2form issues an out of string memory error after completing part of the build when
building a large questionnaire. In2form issues this error message when the In2form
project is too large for the memory resources of your computer. The recommended
minimum hardware requirements for In2form are as follows:
Windows NT 4.0 SP3, Windows 95, or Windows 98 for In2form, In2data, and

In2tab.
Pentium 200 MHz.
32 MB RAM for In2form, and In2tab.

If your computer meets these minimum requirements and you are receiving the above
mentioned error message, try closing all non-essential programs to free up your
computers resources.

Paste Special
If you find that you use the response lists with the same response texts and names in
multiple projects, you may find that creating these response lists as a text file for use
with Paste Special function will save you time. In addition, using a predefined response
list reduces your chances of typing the information incorrectly. Using the Paste Special
function, you can have up to 15 standard response lists with up to 1024 responses per
list.
Note. Using the Paste Special function to enter response lists is similar to using this
function to enter your Language codes and texts when you are creating a control to set
the language of an interview (for more information, see Using Multiple Languages
in the user manual).

Tips and Tricks

To create a text file for Paste Special:

 In a text editor such as NotePad, create a text file in the following format:
[MyHeader1]
MyResponseName1=MyResponseText1
MyResponseName2=MyResponseText2
[MyHeader2]
MyResponseName1=MyResponseText1
MyResponseName2=MyResponseText2

For example:
[Fruit]
1=Apples
2=Bananas
3=Grapes
4=Oranges
5=Pears
[Flowers]
carnat=Carnations
dais=Daisies
roses=Roses
tulips=Tulips
[Standard]
OS=Other Specify
DK=Dont Know
RF=Refused
 Save the file as a text file with the name special.dat in the same directory as the

In2form application (if you have a typical installation, this is C:\In2quest).

Your response lists will now appear in the shortcut menu when you right-click in the
Object Editor dialog box. In2form will display each of the headers you entered in the
text file as selections under the Paste Special menu.
Tip. Your response names can be numeric, alpha, or alpha-numeric. Your response texts
can contain spaces. The response names must be unique within the group of responses
under each header.

10

Chapter 2

Warning. It is possible to include invalid characters in your response names when you
create response lists this way. Do not use the following characters in your response
names: single straight quotation marks (), single curly quotation marks (), straight
quotation marks (), curly quotation marks (), at sign (@), commas (,), periods (.),
equal sign (=), asterisk (*), left square bracket ([), or right square bracket (]). In
addition, you should avoid using braces ({) or (}) unless you want to create a text
substitution for the response text. You should never use braces in the response name.

To use the list in In2form

 Open a form or create a new one.
 In the Form Editor window, double-click the response object.
 In the Object Editor dialog box, select the line where you want to add the response list.
 Right-click, and from the shortcut menu, select:
Paste Special
MyHeader

Your response list now appears in the Object Editor dialog box. You can type additional
responses, change the response names or text, or change the properties for the precodes
on any of the tabs of the Object Editor dialog box. In addition, you can paste additional
response lists using the Paste Special function.
 Close the Object Editor dialog box.
 Close and save the form.

Warning. If you select a line in the response list that contains information and then use
the Paste Special function, you will over-write the previous information. In addition,
each response name value must be unique within the object. If you have pasted a
response list that contains a response name that is the same as another response in the
object, In2form issues a warning when you try to close and save the object. You must
change any duplicate response names before you can save the object.

11

Tips and Tricks

Large Multimedia files

Sending large multimedia files to interview machines in a Computer Aided Personal
Interviewing environment (CAPI) can take a long time. To reduce the time required to
send multimedia files to interview machines, you can distribute the multimedia files on
separate disk to your interviewers. To use these files, you must reference the
multimedia files in In2form to a directory such as C:\Media\FileName. The interviewers
must copy the multimedia files from the disk to a directory on their computer with that
same name (C:\Media in this example). You can also reference the multimedia files
directly to the distributed disk. For example, if the distributed disk is a CD ROM, you
would reference the files as D:\Media\FileName (assuming that the CD drive on the
interviewer machines is the D drive). See Releasing Projects with Large Multimedia
Files on p. 16 for information on releasing projects to the interviewer computers.

To reference the files in each of the multimedia objects in your In2form project:
 On the Value Tab of the Object Editor dialog box, create a parameter (text substitution)

for the file name for the precode. For example: {Picture1}as below.
Figure 2-1 Media files referenced using a parameter in the Object Editor

 Click OK to close the Object Editor dialog box.

12

Chapter 2

Note. If you are creating Video or PlaySound objects using parameters, In2form will
issue error messages informing you that it could not find the file named
C:\In2quest\{ParameterName}, and that you should check that you have specified path
and file name correctly. Ignore these messages (click OK to proceed).
 Close and save the form.
 Select the form in the routing.
 From the menu choose,
Edit
Parameter
 In the Parameters list of the Parameters dialog box, select the parameter you just

created on the form. (For example, TEXTSUBT@Picture1).

 In the Value box, type the file location.

Note. You must type the file location between double-quotes and enter two backslash
marks for each directory level. For example, you type the reference to a file named
MyPic1.bmp located in a directory named Media on the C drive as
"C:\\MEDIA\\MYPIC1.BMP", as in Figure 2-2.
 Repeat for each parameter on the form.

13

Tips and Tricks

Figure 2-2 Referenced multimedia files as parameters

 Click OK to close and save your parameters.

In the Routing, you now have the file reference listed as a parameter next to the form,
as in Figure 2-3,
Figure 2-3 Referenced multimedia files as shown in the routing

Note. If you plan to use Debug, you must have copies of the multimedia files located
in the same folder as you have referenced in the routing.

14

Chapter 2

Tip. You can also use the parameters to reference multimedia files in a CATI
environment. Instead of distributing a disk with the multimedia files, the multimedia
files reside on the network. To do this, each interviewer machine must have the
directory on the network mapped to the same drive label on the interviewer machine.
You would then use this as your file location. For example, if your multimedia files are
in a directory on the network called \\ABCcomp\Current\Projects\Media, and your
interviewer machines have mapped the Projects directory as V:, then you would
reference a file named MyVideo.avi as "V:\\MEDIA\\MYVIDEO.AVI" in the Parameters
dialog box.
Tip. You can also use parameters to reference to reference each part of the file name
and location. For example, you could use a parameter named {Drive} for the drive letter,
{Path} for the directory path, and {File#} for the file name (replacing the # sign with a
number for each file in the object). By entering your parameters this way, you only
need to enter the drive and path information once, rather than for each file.
Figure 2-4 Media files referenced using multiple parameters in the Object Editor

This results in a simpler list of parameters for the form.

15

Tips and Tricks

Figure 2-5 Referenced multimedia files using multiple parameters as shown in the
routing

Tip. You could also create Summit functions in In2script or use other routing controls
to set the {Drive} and {Path} parameters.

Reference to Loop iterations

Referencing Loop iterations from outside the loop results in In2view returning the
wrong iteration information. To reference an item in a loop, you must specify the loop
iteration. You should reference questions asked inside loops using indexes in
parentheses.
If [MyQuestion](1)=1 Then

This tells In2view to look for the response 1 in the form [MyQuestion] in the first
iteration of the loop.
For a nested loop, you would reference in a similar way
If [MyQuestion](1,1)=1 Then

If you want to reference a specific object on the form (where you have more than one
answer object on the form), the loop iteration comes between the form name and the
object name
You must index the form in the following way:
If [MyQuestion](1).[Single1]=1 Then

If you were to write [MyQuestion].[Single1](1) you would be referring to the first

element of the object Single1 on the last answered [MyQuestion] form. By writing
[MyQuestion](1).[Single1] you refer to the object Single1 on the form [MyQuestion]
answered during loop iteration 1. In other words, the first element in the collection of
form objects named [MyQuestion].
The notion conforms to the way users index objects in Visual Basic for Applications.

16

Chapter 2

OLE Automation Error

In2form issues an OLE automation error message when you try to use SPSS Output
although you have SPSS installed on your computer. Conflicting DLL files can cause
this error. Check that the MSVBVM50.dll file is located in your \\Windows\System32
directory and that this file is dated 16 March 1999 or later. If you do not have this file
or if the file you have is of an earlier date, contact the SPSS MR Support center for a
new MSVBVM50.dll file (see the inside front cover of the user manual for contact
details).

In2project
Releasing Projects with Large Multimedia Files
Sending large multimedia files to interview machines in a Computer Aided Personal
Interviewing environment (CAPI) can take a long time.
To reduce the time required to send multimedia files to interview machines, you can
distribute the multimedia files on separate disk to your interviewers.
To use multimedia files in this manner, the files must be referenced using
parameters in In2form. You can reference the multimedia files in In2form to a
directory such as C:\Multimedia and then send a disk with those files to the interviewer.
If you reference the files to the hard drive, the interviewers must copy the multimedia
files from the disk to a directory on their computer with that same name (C:\Multimedia
in this example).
In In2form, you can also reference the multimedia files directly to the distributed
disk. For example, if the distributed disk is a CD ROM, you would reference the files
as D:\Multimedia\FileName (assuming that the CD drive on the interviewer machines
is the D drive).
For more information on creating projects in In2form with multimedia files for
distribution on a separate disk for distribution, see Large Multimedia files on p. 11.

To distribute projects with large multimedia files,

 Create the project as usual in In2project.
 Assign interviewers to the project.

17

Tips and Tricks

 Release the project.

 Send the disk containing the multimedia files to the interviewers.
 If the multimedia files are referenced to the interviewer machines hard drive, have the

interviewers copy the files to the appropriate directory before initiating any interviews
for the project.
 If the multimedia files are referenced to the distributed disk, ensure that the disk is

inserted into the appropriate drive on the interviewers machine before initiating an
interview.
Tip. Multimedia files can also reside on a network drive for CATI projects. The files
are referenced in In2form to the appropriate location on the mapped drive. All
interviewer machines must have this location mapped to the same drive letter.
Normally, In2project places a copy of each multimedia file in each of the interviewer
machines inbox on the local area network (LAN). Referencing multimedia files to the
network will optimize the time required to release projects in a CATI environment as
In2project does not need to place copies of the multimedia files in the machines
inboxes. This also reduces the size and number of files that reside on the network.

Respondent Data Files

You receive two types of respondent data files from the interviewer machines - the i2r
file, and the i2o file. When you collect respondent data, it is the information contained
in these two types of files that In2project transfers to the project database (the .i2c file).

i2r Files - What are they?

The i2r file contains all of the responses to the questions in the interview for the
respondents. In addition, it contains information about the start and end times of the
interviews, information about the project, and information about the interviewer. You
can have i2r files on their own, or associated with i2o files.

18

Chapter 2

i2o Files - What are they?

The i2o is part of the response data from a respondent. In2quest uses the i2o files to
store multimedia responses (such as Pen answers and Recorded Sound answers).
Within the i2r files there are pointers to the related i2o files. Although an i2r file can
exist with out an i2o file, an i2o file must have an associated i2r file.
Unfortunately, you cannot see which i2o file is associated with which i2r file (unless
you are willing to open each i2r file in a text editor and search for text strings ending
in i2o). Therefore, you cannot just delete matching i2o and i2r files. This makes for a
problem if you want to delete some or all of your i2o files to increase the available
space on your hard drive. If you choose to delete all your i2o files, some (possibly all)
of your i2r files will actually be missing some of their information. Because of this, we
strongly recommend that you do not remove your i2o files if you want your backup to
be intact. However, if your data is complete and you feel that the i2o and i2r files are
taking up a lot of space on the hard drive, then we recommend that you take some kind
of hard backup of the files (such as on tape). Once you have a backup of the files, you
can delete both the i2o and i2r files from the backup directory.

Using In2project in a CATI environment

You can use the In2project module of In2quest for Computer Aided Telephone
Interviewing (CATI). In2project functions in much the same way when you use it in a
CATI environment as when you use it in a Computer Aided Personal Interviewing
environment (CAPI). However, there are a few things to keep in mind when using
In2quest in a CATI environment.
You need a license file specific to CATI before you can use In2quest in a CATI
environment. If you do not have the required license file, contact your SPSS MR
Support Centre to receive a new license file (see the inside front cover for contact
information).
 Install In2quest on the server and run In2project and In2view using shortcuts. For more

information, see On Back Office Computers for Computer Aided Telephone

Interviewing on page 3.
 In the Setup dialog box, on the Directories and Miscellaneous tabs, make sure that the

specified directories are folders on the server.

19

Tips and Tricks

You can use Address Management to assign telephone numbers instead of

addresses.
All machines (interviewer machines and the machine running In2project) must

have the same network mapping according to the release path.

Create you Machine and Interviewer lists, then create and release your project

before you set up the shortcuts on the interviewer machines. When you release the
project, In2project automatically creates all the necessary folders.
The transfer of completed interviews from the out-box of the interviewer machines

to the in-box of the back office machine is automatic. Therefore, the interviewers
cannot use the Manual Dial function in In2view nor do you need to use In2comm
to communicate between the interviewer machines and back office computer.
Likewise, the times on the interviewer machines are not synchronized using
In2comms synchronization features.
We also recommend (but do not require) that you set the Auto Collect option in
In2project to Yes in the In2project Settings dialog box, or use the Collect

Respondent File feature.

If you choose to use the Logon feature, and want more than one interviewer to be

able to log onto a machine, then in the Settings dialog box, on the Logon tab, select
the Allow all Assigned Users to Logon feature. Otherwise, interviewers can only
use their assigned machines.
Note. In2project automatically sets the AutoSave option to On in the configuration file
for the In2view machines. You can set a number of other options for the interviewer
machines in the Machine Options dialog box.

CATI Reducing the Number of Log Records

In CATI mode, In2project produces many log records. In2project stores these records
in two tables in the In2project database file (the In2proj.i2p file). You can use
Microsoft Access to reduce the number of records and thus speed up the releasing of
projects.
Warning. Before modifying the In2project database file, you should always make a
backup copy in another directory.

20

Chapter 2

To Reduce the number of records

 Open the In2project database file in Access version 2.0 (if you open this file in a more

recent version of Access, you must open the file as Read Only.)
 Select the Tables tab if it is not already active.
 Open the table named IntMapMail.
 Place you cursor in the column named Mail.
 From the menu, select:
Records
Sort
Sort Ascending
 Select the number of records you wish to delete starting from the lowest number in the
Mail column.
 Make note of the largest number in the Mail column you are deleting as you will need

this information later.

 From the menu, select:
Edit
Delete
Record
 Access warns you that you are about to delete records and that you cannot undo this
action. If you are sure you want to delete the records, click Yes.

Tip. You can use an SQL query instead to perform this action. The SQL string is:
DELETE DISTINCTROW IntMapMail.* FROM IntMapMail WHERE (IntMapMail.Mail<19);

This would result in the deletion of all records with a Mail number smaller than 19.
 Close the IntMapMail table.
 Open the table named LogMail.
 Place you cursor in the column named Mailid.

21

Tips and Tricks

 From the menu, select:

Records
Sort
Sort Ascending
 Select the number of records you wish to delete starting from the lowest number in the
Mailid column to the number equal to the largest number you deleted in the IntMapMail

table.
 From the menu, select:
Edit
Delete
Record
 Access warns you that you are about to delete records and that you cannot undo this
action. If you are sure you want to delete the records, click Yes.

Tip. You can also use an SQL query to perform this action. The SQL string for this is:
DELETE DISTINCTROW LogMail.* FROM LogMail WHERE (LogMail.Mailid<19);

This would result in the deletion of all records with a Mail ID number smaller than 19.
 Close the LogMail table.
 Close the database.

You have now reduced the number of records in the Transaction Log in In2project by
the number of records you deleted in the tables. This should improve the time it takes
to release projects.

To Delete all of the records

 Open the In2project database file in Access version 2.0 (you must use Access version

2.0 for this task as you cannot copy and paste in a file opened as Read Only and you
must not update the database file to more recent versions of Access.)
 Select the Tables tab if it is not already active.
 Copy the table named IntMapMail.

22

Chapter 2

 Paste the table and name it IntMapMailx when prompted for a name.
 In the Paste Options, select Structure only.
 Click OK.
 Delete the table named IntMapMail.
 Rename the IntMapMailx table to IntMapMail.
 Copy the table named LogMail.
 Paste the table and name it LogMailx when prompted for a name.
 In the Paste Options, select Structure only.
 Click OK.
 Delete the table named LogMail.
 Rename the LogMailx table to LogMail.

You have now deleted all the records in the Transaction Log in In2project. This should
greatly improve the time it takes to release projects.

CATI Deleted/Purged projects still appear in In2view

After deleting and purging projects in In2project, some of these projects still appear in
the project list on the CATI interview computer. This can happen if the interviewer
computers did not receive the Close/Delete/Purge information for each step of the
project close down. Each time you Close or Delete a project, you should collect
respondent data as this will also send the necessary information to the interviewer
machines that a project is Closed or Deleted. If you have a number of closed and
deleted projects appearing in the interview machines project list, the quickest way to
clean up the list is to do the following:
 Create a backup copy of the \\In2quest\Release\Lan and under the
\\In2quest\Release\Machine folders. (This is a safety precaution).

23

Tips and Tricks

 Delete all the folders under the \\In2quest\Release\Lan and under the
\\In2quest\Release\Machine folders.
 Once you have done this, you can reopen each project that has a Running status and

de-assign and re-assign the interviewers. By doing this, the project has a "changed"
status thus allowing you to release it again.
 Once you have re-assigned the interviewers, re-release the projects with Running

status.
This should recreate all the necessary directories and files.

CATI Released project does not appear in In2view

Released CATI projects in In2project do not show up on the CATI interviewer
machines. There are three things to check if this happens:
Check that you have the correct license file: In2project (CATI) should we written on

top of the In2project window

Check that you have installation In2quest on a server drive (for example, the H:\

drive). The drive must be the same for the Setup of the In2project computer and all
the interview computers.
Check that at least one of the assigned interviewers uses the Machine ID as

assigned in In2project.
Check that the shortcut to server is correct on the In2view computer. If your server
drive is H:\ then for Machine ID 2 it would be: H:\In2quest\IN2VIEW.EXE
/inifile=H:\in2quest\release\lan\2\in2view.ini

Corrupted i2c File

If you get an error message when collecting data in In2project stating that the i2c file
cannot be manipulated, your i2c file may be corrupted. Often, you can repair the file
using the Repair function in In2form.

To Repair the file

 From the In2form menu choose:
File
Repair
 In the List files of type drop-down list in the Repair project file dialog box, select
All (*.*).
 Select the .i2c file from the list.
 Click OK.

In2form will now attempt to repair the file.

 Once In2form has finished repairing the file, you should be able to collect the data in

In2project.

Synchronizing In2project and In2data

The amount of interviews shown in In2project are more than shown in the In2data
database until you collect respondent data in In2data. You can automate this process
using features in In2quest. There are two parts to the synchronization of the collection
of respondent data in In2project and In2data setting the Auto Collect feature in
In2project and the AutoSync Command-line Parameter in In2data.
The Auto Collect feature in In2project allows you to automatically read data files.
Auto Collect is typically used as a night feature, allowing In2project to read all
collected data files as they are received by In2comm. You can also use this feature
when you are running In2quest in a Computer Aided Telephone Interview (CATI)
environment to read the data files as they are completed.

To change the Auto Collect settings:

 In the Settings dialog box, select the Auto Collect tab (if it is not already displayed).
 Select Yes to start Auto Collect, or select No to stop Auto Collect.

25

Tips and Tricks

By clicking Yes, you can now set the frequency of the Auto Collect by adjusting the
Minutes and Seconds. If you want to set the time of the first collection of data:
 Select the First Time check box (or clear the check box to cancel).
 Set the time for the first time to collect data by entering the time in the box to the left

of the First Time check box. Note that you can enter the time using a 24 hour clock, or
using am and pm. In other words, you can type 17:00 or 5:00 PM (note that you do
not use periods in the abbreviations just am or pm, and it is not case sensitive).
 Click OK.

The AutoSync Command-line Parameter in In2data allows you to set In2data to update
all projects automatically with the new respondent data as In2project collects it. You
use the Command-line Parameter from the DOS Command Prompt. You can usually
find the DOS Command Prompt in the Programs group in your Windows Start menu.
 At the Command Prompt C:\In2quest> type In2data.exe /AUTOSYNC

In2data will now start in AutoSync mode, reading the respondent data files from
In2project as they are received.

Synchronizing Times on Interviewer Machines

When the interview machines connect with the host computer, In2comm synchronizes
the interview machines time and date so that it is the same as that of the host computer.
In2project requires this synchronization for the proper functioning of the assigned call
back times. When you assign Phones and Times to the interviewer machines,
In2project assigns a time interval for each computer.
Without synchronization of the interviewer machine clocks, more than one
interview machine could attempt to connect during an assigned interval. This
synchronization respects time zones. That is to say, if the time interval of the call in
times on the back office computer is 18:00 to 06:00, and the interviewer machine is one
time-zone ahead, then the time interval recorded by the interviewer machine will be
19:00 to 07:00. In this way, the interviewer machines call into the back office computer
during the set time interval (according to the back office computers clock), regardless
of the time difference between the interviewer machines and the back office computer.

26

Chapter 2

Note. This synchronization does not apply when you are working in a CATI
environment. This is because you do not use In2comm to communicate between the
back-office computer and the interview machines. To synchronize times in a CATI
environment, use the network management facilities of your server.

Sending Messages to Interviewers

You can send messages to the interviewers using In2project. You can send messages to
one or more interviewers in the Interviewers List, or to one or more interviewers
assigned to a Project. There are three ways to select interviewers in the Messages to
Interviewers dialog box click the individual interviewer, use the Multiple function to
select a group of interviewers listed consecutively, or use the Tag List function to select
multiple interviewers not listed consecutively.

To set the selection option

 In the Messages to Interviewers dialog box, from the menu choose:
View
Selection
Tag List or Multiple

To send a message to one or more of the interviewers in the Interviewers List

 In the Interviewers window, from the menu choose:
Edit
Messages
 In the Messages to Interviewers dialog box, select the interviewer or interviewers that

you want to send a message to.

 Type the subject of your message in the Subject box.
 Type the message text in the box below the Subject box.

27

Tips and Tricks

Sending the Message

If you want to send the message to the interviewer machines immediately (in a CATI
environment):
 From the menu choose:
File
Send

Tip. You can also send the message immediately by clicking the Release button on the
toolbar (labeled Send Messages when you are working in this dialog box).

If you want to send the message to the interviewer machines the next time they connect
to the back-office computer,
 Click the OK button. (or click the Cancel button to cancel your message).

Illegal Quota Line String error message

You may receive the following (or similar) error messages when releasing projects
with quotas in In2project:
Illegal QuotaLineString:
#VISIBLE:1,0,1,1,1
Syntax error. "" expected at position 1

and
Not a legal quota file:
C:\IN2QUEST\STUDIES\MyProject.QUP

and
Grabbing files to interview MyProject failed.

These errors mean that there is an problem with the syntax of the quota file (*.qup file).
Often this means that two lines in the header of the quota file have changed position.
Someone accidentally editing the quota file is the most likely cause of this problem.

28

Chapter 2

The correct format of the header file is #File, #Version, #Cols, #Names, #Header,
#Visible, #Size as in the following example:
#File: MyProject.qup
#Version: 4.4
#Cols: 5
#Names: "Name", "Visible", "ProjectTarget", "ProjectAchieve",
"MachineTarget"
#Header: "Name", "Visible", "Project target", "Project achieved",
"Machine target"
#Visible: 1, 0, 1, 1, 1
#Size: 20, 10, 10, 10, 10

If the order of the last two lines is switched, then you will receive the above errors. The
#Size line must be the last line in the header line as In2project expects to read quotadata in all lines following the #Size line. To correct the problem, open the quota file in
a text editor and correct the order of the header lines. Then, re-release the project.

In2comm & Remote

Using Communications Software with Call Waiting
Call Waiting tones on your line during a data call will result in disconnection and lost
data. Using In2comm or Remote on a phone line that has a Call Waiting feature can
cause the modem to lose its connection to the carrier (the telephone line) resulting in
the error Modem lost carrier during session (1005). Therefore, we recommend that
you do not subscribe to a Call Waiting service on the phone lines In2comm uses. The
interviewers will also need to cancel Call Waiting on their telephone line during the
transfer of data between the interviewer machines and the back office computer to
ensure successful data communication. Most telecommunications companies provide
a way to turn off Call Waiting on a call by call basis. Often, you can turn off Call
Waiting by inserting the characters *70, (star, seven, zero, comma) before the dialup
number in the dialup information. However, as the code used to turn off Call Waiting
varies by area, be sure to contact your telecommunications carrier to find out the
correct code for your area before doing this. Note that the comma inserts a pause before
dialing the host number.

29

Tips and Tricks

To Turn Off Call Waiting on Interviewer Machines using Windows Modems or TCP/IP
 From the Windows Start menu, select:
Settings
Control Panel
 Double-click the Modems icon.
 Select the modem you are using.
 Click Dialing Properties button at the bottom of the dialog box.
 In the How I dial from this location section at the bottom of the Dialing Properties dialog
box, click the check box next to This location has call waiting.
 In the box next to this, click the down arrow and select the proper code to turn off Call

Waiting. If your code is not listed, you can type the code in the blank space. Be sure to
end the code with a comma to add a pause before the modem dials the telephone
number.
 Click Apply.
 Click OK.
 In the Modems Properties dialog box, click Close.
 Close the Control Panel.

Note. This will turn off Call Waiting only for calls using that modem. Call Waiting will
be restored when the dial-up session ends, and the modem hangs up.

To Turn Off Call Waiting on Interviewer Machines using Standard Modems

 In In2view, click the Program button.
 Click Setup.
 In the Setup dialog box, click Host Communication Setup.

30

Chapter 2

 Click OK.
 If not already selected, click Standard Modem.
 Click Next.
 Click Next again.
 In the first box next to Host prefix/telephone, enter the code to turn off Call Waiting.
Figure 2-6 Example of turning off Call Waiting

 Click Finish.

In2view
Unable to open project
When selecting a project, In2view issues an error message saying that it is unable to
open the project (for example H:\In2quest\Release\Lan\2\In2view.ini). This means that
the project file has been damaged.

To correct the problem:

 Select the active project in In2project.

31

Tips and Tricks

 Open the Assignments window.

 De-assign and re-assign the interviewers for that project.
 Close the Assignments window.
 Re-release the project.

Overflow error message

When starting In2view, it issues an Overflow error message. Problems with the screen
settings on the interviewer machine can cause this error. To correct the problem, reduce
the number of colors in the color palette to 256 using the operating system settings.

Unable to save respondent error message

The only time that In2view reports the error Unable to save respondent is when it is
unable to append the respondent data to an existing i2r-file. The following problems
can cause this error message:
You do not have enough disk space available to save the data.
You are trying to append to a corrupt .i2r file
The .i2r file does not exist (this rarely happens as In2view automatically creates an

.i2r file if there is none),

With In2view, the only module that deletes .i2r files is Remote (the communications
module). However, Remote must receive permission from In2view to delete this file.
If the In2view Remote communication is not working as intended then this may be
the cause of this problem.

In2data
Corrupted database
When opening a database, In2data issues an error message that says that the database
is corrupted.

32

Chapter 2

To Repair the file

 From the In2form menu choose:
File
Repair
 In the List files of type drop-down list in the Repair project file dialog box, select
All (*.*).
 Select the In2data database file from the list (the *.i2d file).
 Click OK.

In2form will now attempt to repair the database file.

 Once In2form has finished repairing the file, open the database in In2data.

Runtime error 51 message

Runtime error 51 is an internal Visual Basic error. The Visual Basic documentation
states that this error is:
"An internal malfunction has occurred in Visual Basic. Unless this call was
generated by the Error statement, use the Product Assistance Request form included
with your documentation to report to Microsoft the conditions under which the
message appeared."
The most probable cause of this error is conflicting DLLs or similar. Contact the SPSS
MR Support center for more information.

Index

Acrobat Reader, 2
Auto Collect, 24
AutoSync Command-line Parameter, 24

LAN, 3
Large multimedia files, 11, 16
License file, 7
license file, 18
Local Area Networks, 3
Log Records, 19
Loop iterations, 15

Backup file, 7

Call Waiting, 28
CAPI, 11, 16, 18
CATI, 3, 5, 17, 18, 22, 23, 24, 26, 27
Colors in In2view, 31
Computer Aided Personal Interviewing, 11, 16, 18
Computer Aided Telephone Interview, 24
Computer Aided Telephone Interviewing, 3, 18
Conflicting DLL files, 16
Conflicting DLLs, 32
Corrupted database, 31
Corrupted i2c file, 23
Corrupted Project, 7

manuals, 1
Modem lost carrier during session, 28
MSVBVM50.dll, 16
Multimedia, 11, 16

Number of colors, 31

OLE Automation Error, 16

Out of String Memory error, 8
Overflow error message, 31

Deleted/Purged projects still appear in In2view, 22

PDF format, 2
Phones and Times, 25

guides, 1

Illegal Quota Line String error message, 27

In2data database, 31
In2project license file, 7
Interview Machines, 5

Quotas, 27

ReadMe file, 1

33

34

Index

Released project does not appear in In2view, 23

Releasing projects, 16
Releasing projects with quotas, 27
Repair, 24, 32
Repair the file, 7
Runtime error 51 message, 32

Sending Messages to Interviewers, 26

Shortcut Target properties, 5
SPSS Output, 16
Synchronizing In2project and In2data, 24
Synchronizing times in a CATI environment, 26
Synchronizing Times on Interviewer Machines, 25

Time and date on the interview machines, 25

Unable to open project, 30

Unable to save respondent error message, 31
Uninstalling In2quest, 7
Using In2project in a CATI environment, 18

Visual Basic errors, 32