Dictionary - Processed Files

  Previous topic Next topic JavaScript is required for the print function Mail us feedback on this topic! Mail us feedback on this topic!  

 

This section of the Dictionary will be the most heavily used section by you - it contains references to all the databases and their fields. Depending on the report template you are working on, you may have only one database listed under "Processed Files" or many entries. The screen capture below shows three database files (Inventory History, Vendors and Products):

 

Sample Dictionary Processed Files

 

The above screen capture shows the Processed Files section of the dictionary. In this example there are three databases in this application:

 

Inventory History

 

Vendors

 

Products

 

For each database you can expand the "tree" to view the database fields that it is made up of. The above example shows the Inventory History tree expanded to show it's database fields. The description for the field is shown under the database name - it is a less cryptic name for the database field name, which is shown in the second column titled 'Name'.  Notice that the database fields shown in the Name column have a prefix (INV:); this prefix is used to identify the database field at it's lowest level. Prefixes allow a programmer to use the same database field name in other database(s) used by this application.

 

The Processed Files section of the dictionary is used to select database field(s) for use in frames, calculated fields, etc. To select a field simply double click the desired field to insert it into the frame or calculated field.

 

ComQuest Dictionary Fields

 

We have made most of the variables used to compile song score data available to you in the Report Builder.  If there is a particular value or score that you do not see in the Dictionary, simply ask us, and we will add it!  If it's a piece of data that has been collected, or that can be calculated based on other data collected, we can easily add it to the Dictionary, and give you access to that variable in your reports.

 

Here is a listing of the available variables in the Song Score reports:

 

clip0013

 

clip0014

 

clip0015

 

clip0016

 

The vast majority of the variables listed above - those prefaced with the "RS:" prefix - are variables stored in the Results.tps data file.  When you run one of the Song Score reports in Report Manager, you will be asked for a start and end date in the Filter screen.  Then, all the variables listed above are calculated for that date range (the week to week trend data is calculated for the 4-week period prior to whatever end date you have specified; all other data is compiled based on the start/end date parameters you've specified).

 

While you obviously won't use all these variables in any given report, they are all nonetheless calculated and stored each time you run a report in Report Builder, and are thus readily available for you to place in any of your reports.

 

The last 13 fields are designed to be used as column and/or report headers.  They contain values such as the text you have entered for each of the radio station call letters, each demo cell or ethnic group, etc.

 

Here is a listing of the available variables in the Respondent Reports:

 

clip0008

 

These are all values stored in the Respondents.dat data file in ComQuest, and they are all available for your use in any Respondent Reports you design in Report Builder. The Cume and Fave settings relate to each of the six stations listed on the Make Calls screen.  If a person said they listened to Station #2 in the first listening box, for example, the value of CUME2 would be 1.  If they didn't listen to that station, the value of CUME2 would be 0 (1 is on or yes; 0 is off or no).  This is also how the listening for the first six radio stations is stored in the respondent record for FAVE1 through FAVE6 (the answer to the second box of listening in the Make Calls screener).  The other variables in the Respondent file should be self-explanatory.