Total Support for the Researcher

Home
Software Solutions
Service Solutions
Customer Support
QueryPartners
News
About TAG
Contact Us
 
   
 
 
 

WinCross - Frequently Asked Questions (FAQ's)

APPLICATION LIMITS

Q: How many rows can be used on a single table? Q: How many rows can be used on a single table?
Q: What is the logic limit in WinCross 6.x/7.x/8.x? Q: How many banner points can I have?
Q: What if my logic requires more than 480 characters? Q: What are “reserved” WinCross names?
Q: What are the record/filesize limits in WinCross?  
 

GENERAL

Q: What are the general rules for rounding in WinCross?
 
Q: Is WinCross 7.0/8.0 compatible with Microsoft Windows Vista operating system?
 
Q: How can I look up an interview respondent who may have provided “dirty” data? Q: Why won't my SPSS file open in WinCross?
Q: Although I have statistics set up to run in my banner, they are not appearing on my tables. What am I doing wrong? Q: Why doesn't my output file look right when I open it in Microsoft Office Word?
Q: When would I want to use indexing?
 
Q. How can I make best use of glossary statements?
Q: Why doesn't WinCross recognize my variable names? Q: What should I do when my results aren’t providing the right numbers?
Q: What are the formulas WinCross uses for its statistical calculations? Q: What is the difference between a table mean and row mean?
 
Q: How do you select only certain tables to run?
Q: How do I use the LOC+ feature? Q: Why don't my numbers look right?
Q: How do I set up weighting in WinCross? Q: Why don’t my statistical tests appear on my tables?
 

STATISTICAL TESTING

SAMPLE BALANCING

Q: What are the critical values for the confidence levels used for statistical testing? Q: What is Sample Balancing? Is it the same as rim weighting? Are negative weights possible?
 
Q: When doing significance testing table lookups, what type of test does WinCross use?  
 

WEIGHTED SIGNIFICANCE TESTING ISSUES

Weighted Standard Error and its impact on Significance Testing (WinCross vs. Quantum & SPSS) A Simulation Comparison of WinCross, SPSS, and Mentor Procedures for Estimating the Variance of a Weighted Mean
Alternative Approaches to Significance Testing with Weighted Means  An Analysis of WinCross, SPSS, and Mentor Procedures for Estimating the Variance of a Weighted Mean

ERROR MESSAGES

Q: Why do I get a “Field width does not match code values” error? Q: Why do I get a “General Protection Fault” error message?
Q: What does the error, “Exceeds records per case,” mean?

Q: What is the logic limit in WinCross 6x/7.x/8.x?

A: 480 characters is the limit when entering logic in a banner, filter or row.  


Q: What if my logic requires more than 480 characters?

A: Use the ASSIGN statement in the Glossary to create new variables.  


Q: How many rows can be used on a single table?

 A: 3,000.

Back to top


Q: What are the general rules for rounding in WinCross?

A: There are three general rules:

Rule 1 - If the remainder beyond the last digit to be reported is less than 5, drop the last digit. Rounding to one decimal place, the number 5.3467 becomes 5.3.

Rule 2 - If the remainder is greater than 5, increase the final digit by 1.  The number 5.798 becomes 5.8 if rounding to 1 digit.

Rule 3 - To prevent rounding bias, if the remainder is exactly 5, then round the last digit to the closest even number.  Thus the number 3.55 (rounded to 1 digit) would be 3.6 (rounding up) and the number 6.450 would round to 6.4 (rounding down) if rounding to 1 decimal.  When the number to the left of the 5 is even, no rounding occurs.  For example, 4.225 would become 4.22.  When the number to the left of 5 is odd, rounding will occur.  For example, 4.215 would become 4.22.     

See page 12 in Hurlburt, R. (1994) Comprehending Behavioral Statistics, Brooks/Cole, Pacific Grove, CA.  


Q: Is WinCross 7.0/8.0 compatible with Microsoft's Vista operating system?

A: The initial release of WinCross 7.0 was tested and released before the Vista operating system was introduced.  An updated release of  WinCross 7.0 addressing known issues with Vista is available on our website for download.  Please contact WinCross Support for this update.  Vista may require some system setting adjustments to accommodate Cryptkey. 


Q: How can I look up an interview respondent who may have provided “dirty” data?

A: You can use the TEST statement in the Glossary to search for respondents that break certain conditions.  


Q: How do you select only certain tables to run?

A: Depress and hold the CTRL key while individually clicking on those tables you want to run, or use the Edit selections button in Run|Tables.  


Q: Although I have statistics set up to run in my banner, they are not appearing on my tables. What am I doing wrong?

A: You must select mean/percentage/chi square for your table statistics as well as for your banner.

Back to top


Q: What should I do when my results aren’t providing the right numbers?

 A: Check your Glossary (Setup|Glossary) to be sure you aren’t overwriting your data. Also check your table filters to be sure you are basing correctly.  


Q: Why doesn't my output file look right when I open it in Microsoft Word?

A: The output file is an ASCII text file without any formatting. You will need to modify the margins, fonts and/or page layout in Word to make the file appear the same as it does in WinCross.

Back to top


Q: How many banner points can I have?

 A: You can program a maximum of 30 banner points.


Q: Why won't my SPSS file open in WinCross?

 A: Your file may be an uncompressed SPSS file - WinCross only supports compressed SPSS files. 


Q: Why do I get a “Field width does not match code values” error?

 A: There is a value wider than the programmed logic (e.g., 1/5:2 (1-99) and there is a value higher than 99).

Back to top


Q: What does the error, “Exceeds records per case,” mean?

 A: 1) Your logic refers to a record number that is greater than the actual number of records in your  data file or
     2) Records per case has not been changed when you run tables, marginal or frequencies.


Q: What are the record/file size limits in WinCross?

 A: WinCross versions prior to 7.0 have a limit of 8,000 characters for variable/ASCII single-record data and 100 records for binary/ASCII multi-card data. WinCross 7.0 has a been increased to a limit of 32,000 and 16,000 variables.

Back to top


Q: Why doesn't WinCross recognize my variable names?

 A: 1) your data file isn’t open or

     2) you don’t have variable names as the first line of your data file or

     3) your logic variables do not match your data file variables.


Q: What are the formulas WinCross uses for its statistical calculations?

 A: The statistical formulas WinCross uses are depicted in Appendix C of the WinCross Users Guide.


Q: Why do I get a “General Protection Fault” error message?

 A: One possible reason (there are many related to Windows operating systems)—At least one “printer” (printer driver) must be installed on the Windows PC even if a print device isn’t physically connected. From Windows’ Start menu, choose Settings|Printers|Add Printer.

Back to top


Q: What is the difference between a table mean and row mean?

 A:  The difference between a table mean and row mean is based on the type of table you’re creating. A table mean is used where every row in the calculation of the mean has only one value. If the rows represent value ranges, then the # (pound symbol) operator must be used to give the row a single value for calculations.

A row mean is appropriate when rows represent a value range and the mean is to be calculated off the actual distribution of data. In that event, a row is created with the appropriate text and logic showing the value range you want to use. In the Row Options dialog box (Setup|Tables|Row Options) you should select the appropriate statistics (mean, standard deviation, standard error, etc.).

Back to top


Q: How can I make the best use of glossary statements?

A: t is not necessary to have glossary statements in a job file in order to run a set of tables, but use of these statements can provide additional assistance and/or solutions to various problems.

COMMENTS

It is common to use the glossary for comments on the study. To create this type of statement an asterisk (*) must first be entered as the first character of that line.

For example:

*PHONE USAGE STUDY, MAY 2004

*COLUMNS 3/70 - 5/80 WERE ADDED TO DATA

ADDREC/ADDLEN

In the occurrence of the lack of “workspace,” additional records can be added to each case as well as additional columns to each record. These are two separate test statements. ADDREC adds the amount of records specified to each case, each record providing 80 columns per case. The syntax is as follows:

ADDREC number of additional records

For example:

ADDREC 2

Similarly, ADDLEN also adds additional “workspace.” This type of glossary statement adds the specified number of columns to the end of each record. The syntax is as follows:

ADDLEN number of additional columns

For example:

ADDLEN 50

(When using these glossary statements, it is imperative that they are the first line within the glossary.)

DEFINE

Variables can be defined in the glossary. This type of statement can be very helpful in creating labels for variables, values or logic statements.

For example:

DEFINE AGE = 1/20

DEFINE YES = (1)

DEFINE NEGATIVE = 1/10:2 (0-3)

DEFINE PPI = {1/6 (1) OR 1/34:2 (8-10)} AND 23/60 (2)

COMPUTE

If mathematical computations are needed, this can be done in the glossary as well by using a COMPUTE statement. This allows the addition (+), subtraction (-), multiplication (*) or division (/) of columns of data.

The syntax is as follows:

COMPUTEnew variable = card/column operator card/column

COMPUTEnew variable = card/column operator value

For example:

COMPUTE 20/10:3 = 1/44:2 + 1/54:2 + 1/64:2 +1/74:2

COMPUTE 3/70:2 = 1/6 * 5

COMPUTE 1/234 = {1/14:2 + 1/30:2} / 2

When adding multiple columns, there is a shortcut:

COMPUTEvariable = card/column A#, where # = number of columns

For example:

COMPUTE 20/10:3 = 1/44:2 A4

(Please keep in mind that the new variable must accommodate a field for a decimal, if necessary.)

TEST

TEST statements are probably the most helpful in determining a solution when “data cleaning” is necessary. TEST statements can also be used for exploration. The syntax is as follows:

TESTlabel = logic for test condition

For example:

TEST XX1 = 1/342:2 (99) and 1/1 ( )

TEST 001 = AGE (1) AND {MARKET (1) ! MARKET1 (1)}

Data Cleaning

When “data cleaning” is essential or data locations need to be changed (such as in a wave study), the use of one and/or two glossary instructions can be utilized.

RECODE

One option is the RECODE instruction. RECODE allows the change of variable values without actually changing the data file. The syntax is as follows:

RECODEcard/column (old value1 = new value1,old value2 = new value2,...)

For example:

RECODE 1/230:2 (99=14)

RECODE 1/12 (5=1,4=2,2=4,1=5)

RECODE 1/109 (C=3)

ASSIGN

The ASSIGN instruction is the second option. ASSIGN allows the addition of information as well as the movement of information to a new or existing location.

The syntax is as follows:

ASSIGNcard/column:width = (value)

ASSIGNnew card/column:width = original card/column:width

For example:

ASSIGN 6/46 = (9)

ASSIGN 10/40:2 = 1/52:2

Note: Be aware that the ASSIGN statement works differently for ASCII and binary data. In ASCII data, the ASSIGN statement works much like the RECODE and replaces the existing value in the specified column, whereas in binary data the assigned value is added to the specified column.

Three features can be used in conjunction with both RECODE and ASSIGN statements. The conditional IF is one additional command.

For example:

IF 1/40:2 (10) RECODE 1/10 (1=2)

IF 1/20 (1) ASSIGN 1/70 = (4)

The second command would be the repeat feature, represented by “R.” This command allows the repeat of the RECODE or ASSIGN statement for multiple columns.

For example:

RECODE 1/57 R10 (1=5,2=4,4=2,5=1)

ASSIGN 1/32 R5 = ( )

The third command is the skip feature, represented by “+.” This command is to be used with the repeat feature. It allows the repeat of statements for multiple columns that are not contiguous, but separated by the same number of columns.

For example:

RECODE 5/23 R5+2 (99=11)

ASSIGN 1/10 R3+10 = (3)

When using glossary statements, note that there is only to be one statement per line with a maximum of 240 characters. As a reminder, any instruction that precedes another instruction must be written first. For example, a statement that creates a variable must appear before other statements referencing that variable. The statements are evaluated from top to bottom, then applied to the data when the tables are run.

Back to top


Q: How do I use the LOC+ feature?

A: The LOC+ feature is used to display data from several positions on one table (sometimes called side-by-side or line tables).

The LOC+ feature can be used for table logic and for banner logic. When the LOC+ is in the tables it will increment the banner columns. When the LOC+ is in the banners it will increment the row columns.

The syntax is:  LOC+(number to add to starting point)

For example:

LOC+5

This will add 5 to the starting point. The starting point is the card/column location in the table’s first row or the banner’s first column, depending on where you are using the LOC.

You can add additional logic to the end of the LOC+5 if necessary. The LOC+ always comes first.

For example:

LOC+5 and 1/10(1)

LOC+ Example

Q.1 Please rate the following attributes on a scale of 1-5

A. Attribute 1          Data position 1/50
B. Attribute 2          Data position 1/51
C. Attribute 3          Data position 1/52
D. Attribute 4          Data position 1/53
E. Attribute 5          Data position 1/54
F. Attribute 6          Data position 1/55

Each respondent rated all 6 attributes using the 1-5 rating scale. You want the rating scale as the banner, with the attributes as the rows on the table.

Banner: 

Q.1 Please rate the following:
----------------------------------------------------------------------------
1=
5=Very 4= 3= 2= Not at
     Sat all Sat mean
--------- --- --- --- ------- -------
1/50(5) 1/50(4) 1/50(3) 1/50(2) 1/50(1) 1/50(1-5)
Table Q1 Filter: LOC+0-5

Table Q1:

A. Attribute 1          LOC+0
B. Attribute 2          LOC+1
C. Attribute 3          LOC+2
D. Attribute 4          LOC+3
E. Attribute 5          LOC+4
F. Attribute 6          LOC+5

Back to top


Q: When would I want to use indexing?

A: Use indexing to create variables which “stack” or “align” data when derotation of the data would otherwise be necessary.

Example of when to use indexed variables:

You have a series of questions asked for different products or brands. Each product/brand does not have a unique set of columns or variables for the questions asked in the series.

The similar variables are “stacked” in an INDEX table in the glossary. Variables within each stack must have the same field width.

I1 I2 I3 I4

IDX (1) INDEX {var1 ,var2 ,var3 ,var4 }
IDX (2) INDEX {var11,var12,var13,var14}
IDX (3) INDEX {var21,var22,var23,var24}

(Items in bold are not part of the glossary index table, but are shown to illustrate the logic that will be used for columns and rows.)

I# corresponds to an indexed variable (column).

IDX corresponds to an individual level of indexed variables (row).

These labels can be used in any logic statement in the tables, banners or glossary.

EXAMPLE:

Respondents were asked a series of questions regarding three different products:
 

1st Prod Asked 2nd Prod Asked 3rd Prod Asked
Q1  1/10 1/35 1/60
Q2 1/11 1/36 1/61
Q3 1/12:2 1/37:2 1/62:2
Q4 1/14 1/39 1/64
Q5 1/15:3 1/40:3 1/65:3
Q6 1/18 1/43 1/68

Q1=Product Code (Prod. A=1, Prod. B=2, Prod. C=3, Prod. D=4, Prod. E=5, Prod. F=6)
Q2=First time purchasing this type of product (yes/no)?
Q3=Number of purchases made for this product (actual number in data)
Q4=Customer Service Rep was helpful (yes/no)?
Q5=Dollars spent (actual number in data)
Q6=Fair price (yes/no)?

Later in the questionnaire, respondents were asked to rate two of three companies and state the date of their first purchase from the same two companies rated:
 

1st Company 2nd Company
Q12  1/100 1/124
Q13 1/101 1/125
Q14 1/102 1/126
Q15 1/103 1/127
Q16 1/104:4 1/128:4

Q12=Store Code (Store A=1, Store B=2, Store C=3)
Q13=Rating scale (Excellent=5, Poor=1)
Q14=Rating scale (Excellent=5, Poor=1)
Q15=Rating scale (Excellent=5, Poor=1)
Q16=Year first purchased from this store

GLOSSARY:

INDEX {1/10,1/11,1/12:2,1/14,1/15:3,1/18,1/100,1/101,1/102,1/103,1/104:4}
INDEX {1/35,1/36,1/37:2,1/39,1/40:3,1/43,1/124,1/125,1/126,1/127,1/128:4}
INDEX {1/60,1/61,1/62:2,1/64,1/65:3,1/68,1/200,1/200,1/200,1/200,1/200:4}
 

I1 corresponds to columns 1/10, 1/35 and 1/60 (Q1)
I2 corresponds to columns 1/11, 1/36 and 1/61 (Q2)
I3 corresponds to columns 1/12, 1/37 and 1/62 (Q3)
I4 corresponds to columns 1/13, 1/38 and 1/63 (Q4)
I5 corresponds to columns 1/14, 1/39 and 1/64 (Q5)
I6 corresponds to columns 1/15, 1/40 and 1/65 (Q6)
I7 corresponds to columns 1/100, 1/124 and 1/200 (Q12 and a blank field)
I8 corresponds to columns 1/101, 1/125 and 1/200 (Q13 and a blank field)
I9 corresponds to columns 1/102, 1/126 and 1/200 (Q14 and a blank field)
I10 corresponds to columns 1/103, 1/127 and 1/200 (Q15 and a blank field)
I11 corresponds to columns 1/104:4, 1/128:4, and 1/200:4 (Q16 and a blank field)

TABLE:

Following is an example of the logic for a table for Q3:
 

Stub Text Row Logic
1 - 10 I3 (01-10)
11 - 20 I3 (11-20)
21 - 30 I3 (21-30)

The filter for this table must include I# or IDX (#) in the logic:

Following are examples of filters to use in place of TN (all respondents) in a table with index logic:
 

I1 (1-6) Corresponds to the codes for all 6 products in Q1
IDX (1-3) Corresponds to all 3 rows in the INDEX table set up in the glossary

Following is an example of a filter used to base the table to one product only:
 

I1(1) Filters the table to only include Prod. A

BANNER:

Example of the logic for a banner for Q1:
 

PROD A PROD B PROD C PROD D PROD E PROD F
I1 (1) I1 (2)  I1 (3) I1 (4) I1 (5) I1 (6)

COMPLEX LOGIC:

Indexed variables & non-indexed variables may be combined in logic statements in any order.

Example: I1 (3) & 1/6 (2,4) can also be written as:       1/6 (2,4) & I1 (3)

SCAN:

Scan logic may be used with Indexed variables to scan across more than one consecutive indexed variable. The scan will scan columns or variables in the data, not index columns, .

Example: I8 S3(5)—Corresponds to all “Excellent” ratings in Q13, Q14 and Q15

(Since WinCross cannot “net” a respondent’s data when using the INDEX option, a respondent answering “Excellent” to Q13, Q14 and Q15 in the above example would count as 3 in the “Excellent” row frequency.)

REPEAT:

The REPEAT feature may be used in the index table. This is a form of shorthand only. It does not reduce the number of index table columns, nor does it in any way combine or relate the variables to one another. A string of three variables designated in the index table as “1/101 R3” would still be three separate variables. If you wanted to include all three variables in a table, you would use the SCAN feature (see above example). The variables to be designated by the REPEAT feature must be of equal width.

The above index table example could also be written as:

INDEX {1/10 R2,1/12:2,1/14,1/15:3,1/18,1/100 R4,1/104:4}
INDEX {1/35 R2,1/37:2,1/39,1/40:3,1/43,1/124 R4,1/128:4}
INDEX {1/60 R2,1/62:2,1/64,1/65:3,1/68,1/200 R4,1/200:4}

Columns 1/10 and 1/11 are still designated as “I1” and “I2” just as columns 1/12:2 are still designated as “I3.”

Note: When more than one series of questions needs to be indexed (whether the next series relates to the same products or another variable altogether), all variables must be incorporated into one index table in the glossary. In the above example, Q2 through Q6 (I2 through I6) relate to the product from Q1 (I1). However, Q13 through Q16 (I8 through I11) relate to the store from Q12 (I7).

Because all index rows (IDX 1 through IDX 3 in the above example) must have the same number of variables, “dummy,” or empty, variables must be placed wherever there is no applicable variable. In the above example, Q12 through Q16 are only asked for two stores for each respondent. The index table has three rows, however, because each respondent was asked Q1 through Q6 for three products. Hence, blank variables are used to fill the last row for I7 through I11 (columns 1/200, 1/200 R4 and 1/200:4).

When dummy variables must be used, it is necessary to either use existing variables that are blank throughout your data file or to add length or a record to your data file.
 

GLOSSARY: ADDLEN 50 Adds 50 blank columns (for each respondent) to the end of your data file.
ADDREC 1 Adds a full blank record (for each respondent) to your data file.

Back to top


Q: What are “reserved” WinCross names?

A: WinCross allows for the use of variable names. However, some variable names are ineligible in that they are reserved for the exclusive use of WinCross.

NET and SUB are two of these reserved WinCross names. The NET instruction shows the total cases included in groups of rows.

For example:

TOP TWO BOX (NET) NET 2
STRONGLY AGREE 1/16 (1)
AGREE 1/16 (2)

The NET instruction is quick and simple compared to the 1/16 (1,2) logic that would have been necessary to achieve the “top two” box.

SUB is used exactly as the NET instruction is used. SUB shows the total number of mentions for a group of rows. For single-response questions, SUB and NET are equivalent.

IDX is another reserved name. This notation refers to individual levels of indexed variables in an index statement.

For example:

IDX (2,3)

There are also a few letter notations that should be avoided when using variable names. These are as follows:
 

R# REPEAT feature M# calc statements for means
S# scan feature V# calc statements for vertical percentages
E# everywhere feature H# calc statements for horizontal percentages
I# index variables # number of columns or variable number
F# calc statements for frequencies

Please refer to Appendix "D" in the WinCross User Guide for a complete list of reserved words and letters.

Back to top


Q: Why don’t my numbers look right?

Note: If using variable data, simply replace the card/column in the examples with the variable name.

A: Numbers don’t look right

Verify your data is clean, your logic programmed correctly, you are using the correct table options and filter and there is nothing in your glossary that is affecting the columns you are checking.

Stray punches/Dirty data

You should first run a marginal to identify any stray punches that might be in your data. If you are checking codes that are more than one digit, it may be easier to run a frequency on those columns.

If stray punches or codes values exist (other than what you believe should exist), your data may not be clean.

To look up respondents, you can use the glossary TEST feature.

Example: If card 1, column 5 can contain valid punches of 1–7 and you have an 8 in your data, you can look up that respondent by using the following TEST statement:

TEST A = 1/5(8)

Once you have identified your respondent, you can clean the data using the ASSIGN statement in the glossary as follows:

IF 1/1:4(0005) & 1/5(8) ASSIGN 1/5 = ( )

where 1/1:4 are the columns for the respondent ID, respondent 0005 having been identified by the TEST statement.
This example cleans the unwanted 8 punch out of that respondent’s data.

If you have several punches that are the outside the accepted range you can clean them all with one ASSIGN statement:

IF 1/5(8) ASSIGN 1/5 = ( )

This cleans all the 8 punches from card 1, column 5 for the entire dataset.

Respondents don’t add to 100

Check to see if you have your filter set for Total. If it is set for Total Answering, your “No Answers” will not add into the total.

Double check your logic to be sure you are including all valid punches/codes.

Back to top


Q: How do I write output to spreadsheets?

A: WinCross tables can be output to several spreadsheet formats. When the Run|Tables|Spreadsheet option is selected, WinCross creates a spreadsheet file(s) in addition to the WinCross ASCII output file.

Other considerations in Run|Tables:

Make sure you have also selected the Create tables option.

Choose the Directory where you want WinCross to write the spreadsheet file(s).

From Write files as type, choose a spreadsheet file type from the dropdown list box. There are these choices: 

• Microsoft Excel
• Lotus 123 1.X
• Lotus 123 2.1
• Lotus 123 3.X

Spreadsheet file(s) default naming:

The spreadsheet file is automatically saved by WinCross in the specified directory using the same name as the first table that is run when the spreadsheet is being created. The file extension is the extension of the spreadsheet file type being created. (For example, if tables Q1 through Q13 are run to an Excel file, the spreadsheet file is named Q1.XLS)

If more than one banner is run, a spreadsheet file is created for each banner. WinCross cannot output more than one banner to a single spreadsheet file. (For the above example, the names for additional files for two more banners would be Q1_2.XLS and Q1_3.XLS)

If the Write each table as a separate spreadsheet file option is selected, the above naming conventions still apply, but each file is named after its corresponding table.

Write each table as a separate spreadsheet file
When selected, a separate spreadsheet file is written for each table.
Write all tables to one spreadsheet file
When selected, all tables are written to a single spreadsheet file.

Note: If more than one banner is run, a separate spreadsheet file is created for each banner.

Note: If the Run|Tables|Interweave banners option is engaged, all of your tables will be written to separate files regardless of the number of banners you are running or the output option chosen.

Choose between the following:

Format percents as percents or Format percents as numbers

Write all text for a row in one cell
Text is written as a continuous line when engaged. This prevents text from wrapping to multiple cells.

Write significance testing to the right of the cell
Significance annotation is printed in the column to the right of the cell when engaged.

Suppress blank lines in the spreadsheet
When engaged, blank lines are removed within the spreadsheet file(s).

Remove
When engaged, the spreadsheet option is removed (deselects the spreadsheet option).

Back to top


Q: How do I set up weighting in WinCross?

A: WinCross has the ability to weight your crosstabs. This is done in the Setup|Banners dialog box and must be done after banner creation.

Weights can be created in three ways:

    1. Weight variables can be part of your original data file

    2. You can use glossary statements to create weighted variables

    3. You can specify an actual value for a weight

To calculate weights for WinCross you must have target percentages.

For example: 

ACTUAL
TARGET
Total Respondents
200 - 100%
Male
  62 -   31%
  80 - 40%
Female
138 -   69%
120 - 60%

Calculation is TARGET/ACTUAL = WEIGHT

  80 / 62 = 1.290

120 / 138 = 0.869

If the weight variable(s) is in the data, this process has been done already. If not, you need to create a weight variable(s) using the glossary as follows:

For example:

IF MALE ASSIGN 1/100:5 = (1.290)

IF FEMALE ASSIGN 1/100:5 = (0.869)

(1/100:5 is the weight field that would be applied for all banner columns.)

If the weight is in your data file or you have created a weight variable in the glossary, specify the weight as the card/column that holds the weight variable. If you plan to use an actual weight value, enter the numeric value. In either case, the weight is specified in Setup|Banners|Weights dialog box.

An actual weight value can have up to 12 digits, can be positive or negative and have decimal places. The negative sign and decimal place count as digits.

Choose the banner column to be weighted. then enter the weight or weight field in the (left) Wgt. variable field. If the same weight or weight field is to be applied to the entire banner, enter the weight or weight field in the Wgt. variable field appearing in the center of the dialog box.

If the weights in your data do not have decimals, indicate the desired number of decimal places in the Implied decimal places field.

Back to top


Q: How do I create a summary table?

Note: If using variable data, simply replace the card/column in the examples with the variable name.

A: To create a mean summary table, your rows will be the question text for the series of tables you are summarizing. Your logic will be the range of values included in the mean calculation.

Mean Summary

Example—Summarize this series of questions:

Please rate the customer service representative on the following, where:
 3=Low, 2=Medium, 1=High and 4=Don’t know

Knowledge – 1/35
Professionalism – 1/36
Empathy – 1/37

The mean summary table would be defined as follows: 

Knowledge 1/35 (1-3)
Professionalism 1/36 (1-3)
Empathy 1/37 (1-3)

Then choose the mean row option for each of the three rows.

If the scale needs to be reversed, your syntax would be defined as follows:
 

Knowledge 1/35 (1-3)#1=3,3=1
Professionalism 1/36 (1-3)#1=3,3=1
Empathy 1/37 (1-3)#1=3,3=1

Again, choose the mean row option for each of the three rows.

Top Box Summary

If you want to create a summary of just the high score your rows would be defined as follows:
 

Knowledge 1/35 (1-4)
Professionalism 1/36 (1-4)
Empathy 1/37 (1-4)
Knowledge 1/35 (1)
Professionalism 1/36 (1)
Empathy 1/37 (1)

The first three lines are the “basing” lines. The last three lines are the lines indicating respondents saying “High.” The “High” lines need to be percentaged off each corresponding “basing” line using the Setup|Tables|Options| Percentage off option.

Since the first three rows are only used for the calculation, you don’t need to show them on your output and can use the Setup|Tables|Row Options|Suppress row option.

Back to top


Q: When doing significance testing table lookups, what type of test does WinCross use?

A: WinCross significance testing is performed using two-tailed tests.


Q: Why don’t my statistical tests appear on my tables?

A: The option to include statistical testing has been added at the banner level, but has not been selected at the table level.

Choose Setup|Tables, then select the table to which you want to add statistical testing. Next, choose Statistics, followed by the preferred tests to run. This process only adds statistical testing to the selected table (as opposed to the banner).

Another way to globally add this option to multiple tables is to modify the table statistics. First, choose Modify|Table statistics. Choose Means, Percentages and/or Chi-Square. Next, select the tables to apply this to (or choose Select All), then choose the Add to existing settings option.

A: Statistical testing has been selected at the table level but not the banner level, or comparison groups in the banner have not been chosen.
Make sure statistical testing has been selected at the banner level. If comparison groups have not been chosen at the banner level, statistical testing selections will not be saved.