SuperWin Features

Open or Create a Project Folder	Create or Top Up Sample File
Set Sample Control Parameters	Set Up Interviewing Dates and Times
Controlling Sample with Quotas	Set Up or Edit Bulletins
Move Appointments	Instruct Stations
Monitor a Station	View Calls, Global Calls and Sample File
Stations File	Users File
View/Edit Menu Database and WinMenu	View Text Files
Report on Calls/Global Calls/Sample/Bookings	Bookings Summary Table
Session Statistics	Impending High Priority Bookings
Outcome by Status	Average Outcome Times
A Simple Quotas Example	Using the Quotas Grid
Columns and Facilities in the Quotas Grid

Creating and Maintaining CATI and Web Survey Projects

SuperWin is used to set up and monitor the sample system when interviewing with DK2Win -$. It is also used to maintain Web Surveys for use with DKWebServe_Adv, to which end there is a DKWebServe_Adv configuration file editor under the File menu (also see section for the Users File below). The button bar is laid out so that, going from left to right, the sequence of functions matches the usual sequence of stages to set up a new project for interviewing.

Open or Create a Project Folder

Enables the creation of a new folder on the server for starting a new interviewing project. Also used to open and monitor existing projects. You can only create new folders for projects if you have Exec user rights.

Create or Top Up Sample File

Quite often, sample data is supplied by the client in Excel or CSV format. However it comes in, it will need to be imported into a database so that a sample file can be created or topped up from it. ViewDBFWin can be used to import the data from CSV format (a format which is easily exported from Excel). Once you have created a database with the sample data, you can use this function to slot fields from the database into the relevant fields of the sample file. You can drag and drop fields from the source database into the relevant slots in the sample file. You can also use expressions to merge multiple fields from the import database into single fields in the sample, for example. DKapture data fields can be optionally specified, defined and then checked to see that they match the relevant compiled file.

Set Sample Control Parameters

The sample control parameters are set from the main screen. These are stored per project and they default to those specified in the sampctrl.txt file in the DKFILES directory. If this file has not been specified yet, then they default to the following values :-

Engaged rebook time 15 minutes

No answer rebook time 90 minutes

5 Questions answered to make appointment file

5 "No Answers" before giving up

3 "Unobtainables" before giving up

20 minutes time limit after appointment time before any interviewer can have it

Give Up Codes :-

Refused
Not Available During Field Work Period
Non-eligible Respondent
Not Applicable
Wrong Number
Other

You can enter numbers for these parameters once in any given project, or you can enter sample file expressions, so that, for example, no answer rebook time can be made dependent on the amount of "TIMESOFAR" or "NUMCALLS" spent on the current respondent. The give up codes are simply outcome texts for extra outcomes for the project. They are not expressions.

Set Up Interviewing Dates and Times

Presents a grid onto which sessions can be entered. A session is defined by the predefined SESSIONS database which contain mnemonics for all sessions with their start and end times, and the associated session number. The mnemonics table also has a column which can be used to set the order of certain mnemonics, by increasing the ORDPREFIX field to promote an item up the list. If mnemonics are of the same ORDPREFIX value, the start time is used to sort the mnemonic. This mnemonics list is presented in the side panel of the sessions grid when you open it. You navigate to the relevant slot in the grid (project by date), and check the sessions you want for that day. You can do outcome pivot tables for any session or set of sessions for any given project. You can also replicate sessions into the future using the pull down in the side panel. When invoked, the grid is filtered so that only projects that have sessions during a period starting at a fortnight before the leftmost column date up to a fortnight after the leftmost column date can be seen. A pull-down menu in the side panel controls this filtering. The current project is exempt from this filtering and is always visible whatever the date in the leftmost column is.

If someone else already has this dates grid open elsewhere, you will not be able to change anything on the grid, but you will be able to view it. In readonly mode, you can see who has got the dates grid open in edit mode from the caption in the window title. If the grid remains locked, despite the indicated user no longer being on the system (happens rarely), then to unlock the grid, simply delete the file \dkfiles\sesslock.txt

Keys and Buttons available are :-

Ctrl+Delete                 Removes a Session
Ctrl+Left and Right         Move to previous/next non-blank session for the project
Shift+Left and Right        Resize columns
Ctrl+Q                      Clears All Sessions Before the Date the Cursor is on
Home                        Go Back to the Current Project Today
Right-Click on Session      Performs a Report of Outcomes, Interviewers or Sessions for that Project
Save                        Save Changes to Any Cells 30 days Old or Newer
Cancel                      Revert to Original Table (Discard Any Changes)

Set Up or Edit Bulletins

This allows a supervisor to set up a message that appears when an interviewer logs in to any particular job. Simply set the job directory as the current job, and then click the Bulletins button (or use the menu option on the File menu). You will either see a list of bulletins for the current job with an option to create a new one, or you will go straight into the bulletin editor. The editor allows you to change fonts and colours of text, bullet points, indents, alignment, left and right margins of paragraphs of text. The interviewer can acknowledge that they have read the bulletin by clicking on the OK button when it is shown on their screen, or they can cancel and read it later. If they acknowledge reading it, this is recorded in the INTNOS field in the bulletins database for that job. They will no longer see that bulletin when they log in to that job again.

Move Appointments

This presents a simple dialog for moving appointments in the current project from one date and time to another. You can also select the outcomes of those you wish to move.

Instruct Stations

With this function, you can tell a station or range of stations, to perform certain instructions at the next convenient opportunity (usually when returning to the front screen after finishing with a respondent). Instructions are as follows :-

Exit DK2Win - After this respondent is finished with, return to the menu system or OS.

Delete Pending Instructions - Remove any unprocessed instructions from the stations' queues.

Show or Hide the advanced options button on the sample control screen. These options enable the interviewer to select the sample respondent they next want to interview, as well as generically search the sample file.

Load a Specific Sample Serial Number - Instructs the first station in the list to load a specific sample member from their current project at the next opportunity.

Reload with a new project and/or serial number - If no serial number is specified, this instructs all the stations specified to load up a new project at the next opportunity (when the current respondent is finished with). If a serial number is specified, just the first station in the specified list is instructed.

These instructions are added to the respective stations' instruction files, so that you can build up a list of actions for any station on the network.

Monitor a Station

Presents a dialog enabling "listening in" and/or visual monitoring of live/all projects. The project is selected in one listbox, which then presents the stations currently interviewing on that project in the other listbox. A Project Monitoring Password must be entered in order to listen in to that project. These are set up using a similar dialog available to exec level users, and activated using the "Project Monitoring Passwords" option on the Edit menu, or by pressing Ctrl+P. To see the interviewer's screen while monitoring, check the "Full Screen Monitoring" checkbox. This will instruct DK2Win.exe to send a snapshot of the screen every few seconds (the interval can be changed by right-clicking on the checkbox). It does this by producing a PNG image of the screen and storing it in DKFILES\SCRN<stn.no.>.png, where stn.no. is the station number of the viewed booth (set by the STN environment variable, for example, SCRN32.png). The SuperWin screen viewer has facilities for changing the screen size, saving the image to a file, and printing the image out. The audio is piped from DK2Win to any listening SuperWins. This means that more than one supervisor can listen into the same booth simultaneously. Sound formats can be set from a menu option available to execs. The right-hand side of the screen displays a simplified view of the interview you are monitoring, so you can visually monitor the survey without using the screen dump facility. Sound streaming is also optional.

View Calls, Global Calls and Sample File

Opens the relevant database in ViewDBFWin. If you are exec status, it opens the databases in READONLY mode, but you can change this to enable editing of the table. If you are supervisor status, it opens the databases in RESTRICTED mode, which prevents the user from making any changes to these tables. The Global Calls file is an audit trail of all calls made for all projects ever. Sample file and Calls file fields are discussed in the DK2Win features section.

Stations File

The stations file is responsible for telling SuperWin how to monitor any particular station. It records the sound format used, the login and logout times, the monitoring sound volume, whether full screen monitoring is called for, the interviewer name and number, the IP and MAC addresses, and the job name in use. These are updated whenever an interviewer logs in to or out of DK2Win.

Users File

The Users file stores details of each user - interviewer name and number, last login date and time, station number, IP address, MAC address, job name, their security level, and their password. To reset a user's password, simply blank out the PASSWORD field and the user will be prompted to set a new password next time they log on. The Users database contains a special field called SECDETS. There are 3 levels of user currently :-

Normal User - SECDETS is blank - user is allowed to use DK2Win without Options menu, but not SuperWin.

Supervisor - SECDETS contains the string "SPV" - user is allowed restricted access to SuperWin, and full access to DK2Win with Options menu.

Executive - SECDETS contains the string "EXC" - user is allowed to use all features of DK2Win and SuperWin. SECDETS must already contain "SPV" for this to be effective.

You cannot use SuperWin without at least SPV level. Even with supervisor permissions, certain functions will only be available to executives. These include :-

Setting the project monitoring passwords

Creating or topping up sample files

Creating a new project directory

Complete access to change any field in the Calls, Global Calls, Users, Menu and Sample databases

Complete access to change any field in the Project data file and Stations file databases

Raw access to the Quotas database (right-click on Quotas button)

Raw access to the Sessions database (right-click on Interviewing Dates and Times button)

Raw access to the Bulletins database (right-click on Bulletins button)

When you are in a Web Survey project directory and there is a DKWebUsers file in that directory, this function will maintain that users file instead of the global CATI one.

View/Edit Menu Database and WinMenu

The menu database has the following structure :-

Field Name	Field Type	Length	Description
ORDER	NUMERIC	9 with 3 decimals	Sets the menu row this item is displayed on
CAPTION	CHARACTER	100	This is the text that appears on the menu
ACTION	CHARACTER	200	This is the command that is executed when the user chooses this menu item
MONIPASS	CHARACTER	50	The password required to monitor the job launched by this menu item (encrypted - see Monitor a Station for details)
VISIBLE	LOGICAL	1	Sets whether this menu item is visible on the screen
ENABLED	LOGICAL	1	Sets whether this menu item is accessible or greyed out
AUTORUN	LOGICAL	1	Sets whether this menu item is automatically launched when the menu is loaded by WinMenu

WinMenu uses this database to generate and display a menu for launching jobs from interviewers' screens. It takes the following command line switches and arguments :-

WinMenu [menu-database] [-k] [-l] [-ppassword] [-tXXX "command to run"]

menu-database is the name of the menu you wish to load up. If omitted, it uses the DKMENU.DBF file in the current drive's \DKFILES directory.

-k means keep the Windows task bar, rather than hiding it to limit interviewers' access to the PC.

-l means left-align the menu items rather than centre them on-screen.

-ppassword means do not allow the user to leave the menu unless password is entered when prompted. This prevents an interviewer from clicking outside of the WinMenu window to try to access another program.

-tXXX "command to run" means set a timeout of XXX seconds, after which period of inactivity "command to run" is executed. This allows a user who is logged in to the PC and has left the PC running WinMenu, to be automatically logged off using the "shutdown.exe -l" command after some period of inactivity, for example.

eg. WinMenu -l -k -pmj -t600 "shutdown.exe -l"

would left-align menu items, keep the Windows taskbar on-screen, set a password to exit of "mj" and an inactivity timeout of 10 minutes before a shutdown command is run.

The ACTION field has some special mnemonics :-

LOGO graphic-filename means place the image in graphic-filename at the top of the menu.

MENU menu-database means this item is a submenu whose items are defined in menu-database, a database whose structure is identical to the main menu database above.

EXIT means close this menu. If it is a submenu, then return to the menu that launched this one.

When empty (ie. no ACTION field has been specified or it is entirely blank), then the text in CAPTION is displayed greyed out and the item is for display purposes only (it cannot be navigated to using the mouse or keyboard).

If you Right-Click on the menu presented by WinMenu, then you can set the menu item font, you can refresh the menu (in case the underlying database has been changed since WinMenu was loaded, although WinMenu should automatically reload if it detects the database has changed), and you can view the command associated with the menu item you are on.

View Text Files

Shows a list of all the textual files (*.TXT, *CFG, *.CSV, *.HTM*) in the current project directory, and selecting one launches it in your default text editor (usually Notepad).

Reporting

There are numerous reports that have been built in to the SuperWin program :-

Report on Calls File/Global Calls File/Sample File/Bookings Listing

These dialogs enable a customisable listing of records which you can filter and sort using parameters on the dialog. Output can be plain text, rich text format (Word), or HTML format (browser). The system uses customisable templates which can be redesigned or tweaked using ViewDBFWin. These templates are stored as follows (where F: represents the DKapture installation drive) :-

File Path and Name	Description
F:\DKFiles\macstpls\Calls_Listing.tpl	Plain Text Calls File Listing
F:\DKFiles\macstpls\Calls_Listing_rtf.tpl	Rich Text Calls File Listing
F:\DKFiles\macstpls\Calls_Listing_htm.tpl	HTML Calls File Listing
F:\DKFiles\macstpls\Sample_Listing.tpl	Plain Text Simple Sample File Listing
F:\DKFiles\macstpls\Sample_Listing_rtf.tpl	Rich Text Simple Sample File Listing
F:\DKFiles\macstpls\Sample_Listing_htm.tpl	HTML Simple Sample File Listing
F:\DKFiles\macstpls\Sample_Listing_Detailed.tpl	Plain Text Detailed Sample File Listing
F:\DKFiles\macstpls\Sample_Listing_Detailed_rtf.tpl	Rich Text Detailed Sample File Listing
F:\DKFiles\macstpls\Sample_Listing_Detailed_htm.tpl	HTML Detailed Sample File Listing

Bookings Summary Table

This dialog allows you to summarise bookings for the current project, by grouping them into time slots, and by priority or interviewer. It presents a pivot table which counts the number of bookings in the selected slots.

Session Statistics

This function generates a series of pivot tables of Call Outcome by Interviewer Number, into one long HTML document which is then launched in your browser. It first asks you for a time and date, which defaults to now, (with an option to select the whole day), and it uses this to decide which sessions are to appear in the report. It uses the current session (closest to the input date and time) if we are more than 1/4 of the way through it. It uses the preceding session otherwise, unless you have chosen "Whole Day", in which case it gives you stats on all sessions that day. Having worked out the session, it then lists the jobs with calls in that period. You check the projects you want stats on, and SuperWin then calls up ViewDBFWin to produce the HTML pivot table output which is presented to you in your default browser. Before doing the pivot tables on these calls, SuperWin coalesces the durations of "Answered" outcomes into their subsequent outcomes, if known at the time the tables are produced. You can choose to display Counts, Total Times, or Average Times, in the pivot tables produced. Tables are produced from the Global Calls File.

Impending High Priority Bookings

This allows quick and easy reporting of high priority bookings that are imminent. The dialog allows you to choose the highest priority level allowed in the report, and how far ahead into the bookings you wish to look. It then collates the relevant entries by job name, and presents a list of these jobs on screen. Here you can see the number of high priority bookings there are and the number of people currently working, for each job. Pressing Enter on any job will list the high priority bookings details for that job.

Outcome by Status

Does a quick pivot table for the current project's sample file of Outcome by Status. This allows you to view the spread of status codes by outcome, to see the state of the sample file. Press Ctrl+Alt+O to quickly generate this report. The current STATUS codes are :-

Status	Meaning
0	Fresh
1	Finished With (Complete, Refused...)
2	Appointment
3	Held Up Fresh
4	Being Interviewed
5	Held Up Appointment
7	*Internal* Fresh Pending Release
9	*Internal* Appointment Pending Release

Average Outcome Times

Does a quick pivot table for the current project's CALLS file of Outcome by Average Duration in minutes. This lets you see how long interviewers are taking reaching certain outcomes. Press Ctrl+Alt+T to quickly generate this report.

Quota Groups and the Quotas Screen

Quotas enable more precise control of what sample is interviewed as conditions change during interviewing. The system is very flexible, to allow for more complete control over what sample ends up on interviewers' screens. As a result, advanced quota control can be technically challenging to some. DK Computing can always provide "hand-holding" for new users, and expert advice and tuition for the more adventurous supervisors. For details on the precise logic used in handling quotas, please read this technical addendum.

Every time a data record is written by the DK2Win sample system, each quota record with a DKDATADEF field filled in, is updated with the current HAVEGOT and UPTORECNO fields from the DKapture data file. HAVEGOT represents how many DKapture data records match the DKDATADEF field, and UPTORECNO represents the number of DKapture data records it has counted through so far (usually the number of data records in the DKapture data file).

A Simple Example - You only Require Interviews from 100 Cornish People :-

Add a new record to the quotas table by down-arrowing from the last record, or click the plus-sign button in the navigation control

Enter a database expression into the SAMPLEDEF field which defines Cornish people in terms of sample file fields. For example,

'CORNWALL' $ UPPER(DKDATA5)

Enter a DKapture expression into the DKDATADEF field which defines Cornish people in terms of DKapture data fields. For example,

QREGION 7

Enter the number 100 into the TARGET field

Double-click the QUOTA_TYPE field and choose type "3) Restrict Sample"

Give the quota a number and description in the relevant fields

Using the Quotas Grid

You can multi-select quota records (using Ctrl, Shift, Arrow Keys, and the mouse) - selected records have the QUOTA_IDX field highlighted in yellow. Then you can press enter on the MANACTION, TGTACTION and/or QUOTA_TYPE fields and set them for all the selected records in one go.

You can select multiple quotas (using the Ctrl+Click to toggle a record's selected state) and then click the filter button (or use the menu option under Actions) to view all sample records that match any of the selected quotas' SAMPLEDEF fields. You can also order the Quotas in such a way as to see the groups closest to completion at the top of the table, or in many other orders using the Ordering menu.

Columns and Facilities in the Quotas Grid

QUOTA_IDX lets you give a quota row a number, so as to order the grid in your preferred order. This should uniquely identify the quota record.

DESCRIPTIO lets you give a quota row a description, so as to more easily identify what it is for.

MANACTION is one of NOACTION, HOLDUPB, HOLDUP, or RELEASE. If it is blank, it is deemed to be NOACTION. One these 4 actions is undertaken for each quota type 0, 1 or 2 record, when you call the "Process Manual Quotas" menu option.

NOACTION means do not hold up any matching sample records or delete any bookings associated with these records.
HOLDUPB means hold up any matching sample records and delete any bookings associated with these records. If the field HUPBEXPR is not empty, and the sample member we are considering has an appointment, the logical expression in this field, in addition to the other normal tests, will be used to determine whether the action will be taken or not.
HOLDUP means hold up any matching sample records but leave any bookings associated with these records.
RELEASE (or blank) means return any matching sample records to the free sample pool.

This field is updated whenever a type 2 quota hold up or release is activated from a {QUOTA...} directive in the questionnaire.

TGTACTION is the action taken when the quota's target has been met.

HUPBEXPR comes into effect whenever either action field (MANACTION and TGTACTION) is set to HOLDUPB. If HUPBEXPR is empty or the action field we are concerned with is not HOLDUPB, the expression is not used to determine whether the action should take place or not. If the action field we are processing is HOLDUPB, and the sample member we are looking at has an appointment, and the HUPBEXPR field is a logical expression that evaluates to .T. or is an empty field, the action is taken (dependent on the other usual considerations). For example to only hold up bookings with a priority greater than 100, HUPBEXPR could contain PRIORITY>100.

SAMPLEDEF is where you enter a database expression which evaluates to .T. (true) for all sample records that are in this quota.

LASTACTION records the action that was last performed for this quota.

Held Up - Bookings Suspended matches HOLDUPB in the TGTACTION or MANACTION fields.
Held Up - Bookings Preserved matches HOLDUP in the action fields.
Released matches RELEASE in the action fields.

DKDATADEF is the DKapture expression (true or false expression in the DeditWin advanced search format, eg. QKQUOTA1 3,5-8) which is used to count the records in the DKapture data file, so as to ascertain whether a target is being approached or reached. This "counting up" procedure is activated by a {QUOTA ...} construct somewhere in the questionnaire, or when a data record is written, depending on quota type.

TARGET allows you to set a target for the quota row. The TGTACTION is performed when this target has been met. The evaluation of counts and whether targets have been met is done inside the questionnaire when a relevant {QUOTA...} construct is encountered for type 2 quotas, or, on type 1 quotas, when a data record is written. For type 0 (Count Up) quotas, a manual instruction to hold up and release from Superwin's Quotas screen, will cause type 0 quotas to action. For restrict-type (type 3) quotas, this field is checked when retrieving the next sample respondent for the interviewer's screen. If this field is not filled in (is blank or zero), then the target is deemed never to have been met, irrespective of what figure is in the HAVEGOT field. Also see ADDONEXPR below.

HAVEGOT records the number of DKapture data records that match this quota's DKDATADEF definition.

UPTORECNO records the number of DKapture data records used to count up into HAVEGOT.

COUNTUPSPL records the number of sample records that match the SAMPLEDEF expression, for each quota row in the grid. It is filled in when you count up the sample records matching each quota group for any combination of Status and Outcome codes, or for all sample records. The SAMPLEDEF expression field (a logical expression for each quota record) controls whether the sample is counted for any given quota group. Use the "Count Up" or "Refresh COUNTUPSPL" options on the Actions menu, and the field/column COUNTUPSPL is filled with the number of sample records matching each quota record. If the sample file has a field called QUOTAGRPS, then this is filled to its width with comma-separated matching quota group numbers (from the field QUOTA_IDX).

QUOTA_TYPE can be one of the following values :-

0) Count Only - For counting up purposes only - can be used for holding up or releasing.

1) Auto - For counting up, and triggering hold up or release when a target has been reached. These are automatically checked whenever a data record is written, in order to ascertain whether any hold ups or releases should be done. Target must be met and greater than zero for an action to be taken automatically.

2) {QUOTA} - For counting up, and triggering hold up or release when a target has been reached. These are used when you embed a {QUOTA ...} directive in a question. These are not checked automatically when a data record is written. Target must be met and greater than zero for an action to be taken.

3) Restrict Sample - For filtering out undesirable sample records before they are put onto an interviewer's front screen. If the condition in SAMPLEDEF is true for any of the matching type 3 quota records, and the corresponding quota record's HAVEGOT equals or exceeds the TARGET, then the sample record is not allowed into the interviewing system. Very complex tests can be performed to vet sample records. The SAMPLEDEF field can contain the mjstats function to count, sum or average any expression derived from the sample record, matching certain criteria. Since the context for evaluation of the SAMPLEDEF expression is the sample file itself, the call to MJSTATS can omit the first database argument if it is to be evaluated on the sample file. Target must be met and greater than or equal to zero (including a blank target) for the restriction to take place.

4) Accept Sample - This is simply the opposite of type 3. The condition in the SAMPLEDEF field is tested. If it is false, and the corresponding quota record's HAVEGOT equals or exceeds the TARGET, the sample does not come onto the interviewer's screen, otherwise it is tested for the normal conditions (appointment time, interviewer number ...) and appears on the screen if these conditions are met. Target must be met and greater than or equal to zero (including a blank target) for the acceptance to take place. If there is at least one type 4 "Accept Sample" quota record, then one of these quotas must be true for sample to come through to the interviewer. Restricts take precedence over Accepts so if you have a sample member that fulfills both a Restrict quota and an Accept quota, the sample member will be restricted, not accepted.

10) Order Appts. - For imposing an alternative ordering on the sample for getting appointments. Bear in mind that sample appointments are denoted by having a STATUS field of 2. The SAMPLEDEF field is evaluated to ascertain whether it is true or false. If it is true, the index order specified in the ADDONEXPR field is used to order the sample file when getting the next respondent appointment. If not, each type 10 is evaluated in QUOTA_IDX order, until one is found which gives true. If none are found, the default ordering is used. For appointments, the default ordering is defined by this expression :-

IF(STATUS=2,'A','Z')+DTOS(APPT_DATE)+APPT_TIME+STR(PRIORITY)

When the index order is set for retrieving appointments, the sample file is positioned on the first record in that order, and each one is checked for viability against the type 3 quotas (if there are any) and, if its appointment time and date are before now, it automatically selects the sample record with the most urgent priority. You will need exclusive access to the sample file with ViewDBFWin.exe in order to create the alternative appointment fetching indexes. When creating an alternative index order for appointments, you should start the expression with IF(STATUS=2,'A','Z')+... so that appointment records are at the top of the list. As soon as a non-STATUS 2 record is encountered, checking for appointments stops.

11) Order Fresh - For imposing an alternative ordering on the sample for getting fresh sample records. Bear in mind that fresh sample is denoted by having a STATUS field of 0. The SAMPLEDEF field is evaluated to ascertain whether it is true or false. If it is true, the index order specified in the ADDONEXPR field is used to order the sample file when getting the next fresh sample record. If not, each type 11 is evaluated in QUOTA_IDX order, until one is found which gives true. If none are found, the default ordering is used. For fresh sample, the default ordering is defined by this expression :-

STATUS

When the index order is set for retrieving fresh sample, the sample file is positioned on the first record in that order, and returned as the next fresh sample record, if its STATUS field is zero or blank. You will need exclusive access to the sample file with ViewDBFWin.exe in order to create the alternative fresh sample fetching indexes. When creating an alternative index order for fresh sample, you should start the expression with IF(STATUS=0,'A','Z')+... so that fresh sample records are at the top of the list. As soon as a non-STATUS 0 record is encountered, checking for fresh sample stops.

If any of the quota records release sample, all "Count Only", "Autos", and "{QUOTA" type HOLDUP and HOLDUPB quotas, which had been actioned before (as denoted in the LASTACTION field) are performed again, to ensure that records which occur in both a released group and a held up group, are always held up. Basically, hold-ups have priority over releases.

SAMPLENAME dictates which sample files this quota is for. If it is blank, then it is for all sample files, otherwise this field should contain the name (without any path or extension) of the sample file it is for. If specified, this quota record is only ever considered for the sample file it specifies.

ADDONEXPR and CCQ are numeric expressions (blank for zero, "1" for add one etc.) that are evaluated in the context of the sample file, and the results added to the count, before comparing with the desired TARGET field. They "adjust" the count before comparing with whatever is in the TARGET field, to see if hold up or release is warranted. The field HAVEGOT always reflects the data records that matched DKDATADEF from the DKapture data file and ignores ADDONEXPR and CCQ. For QUOTA-TYPE 10 or 11 records, ADDONEXPR contains the index order name imposed when checking for bookings and fresh sample from the sample file, when the SAMPLEDEF expression evaluates to true.