The FastFinder feature is useful when you need to define a very long list of response items. It enables you to access response items stored in an external database via a DSN connection and an ODBC query.
During data collection, the Interviewer will be presented with a refined choice of items, based on the characters he or she typed in a preceding open question. Using this option not only saves the Interviewer time, but also ensures that the syntax of responses contained in the final data will be identical to that of your original list.
You can set up a FastFinder in two different ways:
Let’s take the example of a list items containing all the cities in Great Britain. This list is stored in an MS Access *.mdb file, more specifically in a table called "GreatBritain", in the field "Cities". After specifying the DSN of the *.mdb file we will write the following SQL query:
SELECT Cities FROM GreatBritain
FastFinder will propose those response items, cities, whose name start with the first characters typed in by the Interviewer. The Interviewer can then select the appropriate response by using the keyboard's arrow keys.
A refined FastFinder enables you to make a preliminary selection from the list of response items, based on answers given by the respondent at a previous question. As with the example above, let's consider a list of all the cities in France. This list is stored in an MS Access *.mdb file, more specifically in a table called "France", in the field "Cities". The table "France" also contains a second field called "Department", containing each city’s respective numerical department code [e.g. Paris: 75, etc...].
Immediately preceding the FastFinder question, we create a Numeric question, ??DptCode??, in which we ask the respondent the department code. You will want to set the minimal and maximal values of this question so that only valid departments can be entered.
On the FastFinder question, we click Fast Finder, and specify the DSN of the *.mdb file. For example:
It is also possible to specify an ADO connection string, which alleviates the need to set up DSN on each machine. The format is as follows:
Provider=sqloledb; Data Source=[Your SQL Server]; Initial Catalog=[SQL Database you want to use];Trusted_Connection=no;User Id=[SQL Login];Password=[SQL Login Password]
If you are using a Microsoft Access database, you can set an ADO string as follows:
Provider= Microsoft.Jet.OLEDB.4.0;Data Source=c:Database1.mdb
If your Access database is protected by a password, then, you need to provide the password in the connection string, for example:
Provider= Microsoft.Jet.OLEDB.4.0;Data Source=c:Database1.mdb;Jet OLEDB:Database Password=askia;
We then enter the SQL query, for example:
During data collection, FastFinder will present the response items (cities) whose names start with the first characters typed in by the Interviewer, from a list which has been reduced to towns contained within the Department specified in ??DptCode??. The Interviewer can select the appropriate response by using the arrow keys on the keyboard.
It is possible to simulate FastFinder functionality in Web interviews. You need to crate a DSN called "BDDAskia" and associate it with the database. This can be tested in screen mode.