CHRR

CHRR
NLS Investigator for
Windows 95

NLS CD-ROM
User’s Guide

Appendices

Appendix 1 - Menu Commands
Appendix 2 - File Names
Appendix 3 - Sample Print Files
Appendix 4 - Extract Files
Appendix 5 - Common Errors

Appendix 1

CHRR NLS Investigator - Main Menu Bar

Menu Components

	Command	Description	Shortcut
File
	New Tagset	Open a new, blank extract specification file.
	Open Tagset	Re-open an existing extract specification file.
	Save Tagset	Save selected variables in an extract specification file.
	Save Tagset As	Save selected variables in a renamed extract specification file.
	Write Documentation	Create printable text documentation files.
	Exit	Close the program.
Window
	Default	Reset NLS Investigator windows to the default arrangement.		Alt+0
	Cascade	"Stack" the child windows in NLS Investigator.
	Tile Horizontal	Horizontally arrange the child windows in NLS Investigator.
	Tile Vertical	Vertically arrange the child windows in NLS Investigator.
	Contents Window	Switch to the Navigation window.		Alt+1
	Variables Window	Switch to the Variable List window.		Alt+2
	Text/HTML Window	Switch to the Text/HTML window.		Alt+3
Extract
	Review Tagged Variables	Review selected variables.
	Extract Tagged Variables	Create an extract with selected variables.
Data
	View Case	Select one case and view its data values.
	Close Case	Stop viewing the selected case.
Options
	Font	Change the appearance of text.
Help
	About	Display version information.
	Contents	Not currently linked.

Appendix 2

File Names

After selecting one of the options and naming the extract specification file, a three-letter default file extension will automatically be attached to the name entered. Depending on what data set was originally chosen in the Cohort Box, the file extension for the extracted specification file will be one listed in the Extract File Types below. The name of the current working file is identified in the CHRR NLS Investigator Title Bar (blue bar) as Data Set: [Tagset: file_name]. If it is a new file, the file name will be [Tagset: untitled] until it is given a name when the "Extract Tagged Variables" option is activated.

Extract File Types

The extension depends on the data set used.

*.MSR	Men, extract specification file used to store variables.
*.BSR	Boys, extract specification file used to store variables.
*.WSR	Women, extract specification file used to store variables.
*.GSR	Girls, extract specification file used to store variables.
*.YSR	NLSY79 Youth, extract specification file used to store variables.
*.CSR	Child, extract specification file used to store variables.

All files subsequently created in conjunction with the extract file will use the same 8-letter file name, and depending on the file type to be created, one of the following extensions will be attached.

(tagset_file_name).CDB	codebook print files of the total universe codebook for the selected variables.
(tagset_file_name).DAT	extracted data files containing the selected variables.
(tagset_file_name).DCT	Stata dictionary file.
(tagset_file_name).DOC	index print file listing the selected variables with descriptive statistics.
(tagset_file_name).SAS	SAS control cards.
(tagset_file_name).SPS	SPSSX control cards.

Documentation Files

Below is a complete list of files that can be produced when the ‘Write Documentation" option is chosen from the File component of the Main Menu. Documentation files are given the default extension of .txt

Anyword.txt	Any word in context index.
Keyword.txt	Keyword in context index.
Record.txt	Record number index.
Year.txt	Year index.
Varname.txt	Variable name list.
Question.txt	Question name list.
Codebook.txt	Complete codebook.

Appendix 3

Sample Print Files

As a result of the "Write Documentation" function, print file(s) are produced and placed in the output directory. The location, names, and characteristics of each file are specified at the time of printing as described in Chapter 5 - Write Documentation. The extensions for these files are .txt.

The following files are displayed in this section

Any Word in Context Index

Anyword.txt

Codebook

Codebook.txt

Key Word in Context Index

Keyword.txt

Question Name List

Question-name.txt

Record Number Index

Record.txt

Variable Name List

Varname.txt

Year Index

Year.txt

Anyword.txt

Codebook.txt

The codebook file (.txt) created with the Write Documentation function is identical in format to the codebook file (.CDB) created with the Write Codebook file. The difference is the number of records produced. The codebook file (.txt) is the complete codebook of all the variables in the data set. The codebook file (.CDB) is only for those variables in the extract specification file. The file below is abbreviated.

Keyword.txt

Question-name.txt

Record.txt

Varname.txt

Year.txt

Appendix 4

Files Generated

Sample Extract Files

Extract files were created as a result of Performing an Extract . The following extract files are displayed in this section.

Chld--88-2ndpreg.CDB	Codebook file for the variables extracted.
Chld--88-2ndpreg.DCT	Stata Dictionary file for the variables extracted.
Chld--88-2ndpreg.DOC	Documentation File to Document the Raw Data File (*.DAT)
Chld--88-2ndpreg.SAS	SAS file.
Chld--88-2ndpreg.SPS	SPSS file.

Chld--88-2ndpreg.CDB

Chld--88-2ndpreg.DCT

Chld--88-2ndpreg.DOC

Chld--88-2ndpreg.SAS

Chld--88-2ndpreg.SPS

Appendix 5

Common NLS Investigator CD-ROM Errors

Caution!

It is important to remember that although CD-ROM disks are practically indestructible, careless handling can permanently damage them. A very small scratch can render a disk unusable. Fingerprints and other dirt can cause fatal errors during program execution. Even microscopic dust particles can cause problems.

Anything you do to reduce disk handling is desirable. CD-ROM drives which use disk caddies have become common. A disk caddie for each CD-ROM you own may seem to be an unnecessary added expense, but it can be well worth the cost if it protects even one of your expensive CD-ROM disks. If you have to handle a CD-ROM disk, handle it only by the edges. NEVER touch the data surface of the disk (i.e., the bottom, shiny side without printing). Don't lay CD-ROM disks on anything. Use caddies or jewel cases to store them.

Error Messages

Error messages generated by NLS Investigator appear in the following format:

Run-time error nnn at xxxx:yyyy

Where,

nnn is the error number, found in the list on the following pages; and
xxxx:yyyy is the error address, that is useless except during program development.

The errors come from Borland Pascal with Objects Version 7.0^™ manual. More information about all errors can be found in Borland's Programmer's Reference Manual.

DOS Errors

1	Invalid function number.	{You should never get this}
2	File not found.	{Often associated with CD-ROM drives connected via a network. Try the disk on a PC with a locally connected CD-ROM drive. You can compare directories produced with both setups. Usually the network directory will not show all the files.}
3	Path not found.	{You should never get this}
4	Too many open files.	{The program has too many open files. You probably don't have a FILES=xx entry in your CONFIG.SYS file or the number (xx) is too small. Add FILES=20 or increase the number to 20 and reboot your computer.}
5	File access denied.	{You should never get this}
6	Invalid file handle.	{You should never get this}
12	Invalid file access code.	{You should never get this}
15	Invalid drive number.	{You should never get this}
16	Cannot remove current directory.	{You should never get this}
17	Cannot rename across drives.	{You should never get this}
18	No more files.	{You should never get this}

I/O Errors

100	Disk read error.	{Sometimes this input/output error occurs because of faulty hardware or a dirty or damaged CD-ROM disk. What has happened is that a data field has been read incorrectly. This causes the program to attempt to read beyond the end of file.}
101	Disk write error.	{Your output disk is full}
102	File not assigned.	{You should never get this}
103	File not open.	{You should never get this}
104	File not open for input.	{You should never get this}
105	File not open for output.	{You should never get this}
106	Invalid numeric format.	{You should never get this}

Critical Errors

Critical errors will usually terminate the program. They often are caused by faulty hardware or dirty CD-ROM disks. For more information refer to a DOS programmer's reference manual.

150	Disk is write protected.
151	Unknown unit.
152	Drive not ready.
153	Unknown command.
154	CRC error in data.
155	Bad drive request structure length.
156	Disk seek error.
157	Unknown media type.
158	Sector not found.
159	Printer out of paper.
160	Device write fault.
161	Device read fault.	{The most common hardware problem usually indicates a damaged or dirty CD-ROM disk. Usually this occurs during data extraction. If the error occurs at the same place repeatedly, the CD-ROM disk is probably damaged; otherwise, the CD-ROM drive may be faulty or the CD-ROM disk may be dusty or fingerprinted.}
162	Hardware failure.

Fatal Errors

Fatal errors immediately terminate the program.

200	Division by zero.	{You should never get this}
201	Range check error.	{This error is known to occur with certain mouse drivers. It MAY have been corrected. If it recurs, try rebooting without the mouse driver installed in CONFIG.SYS or AUTOEXEC.BAT.}
202 203	Stack overflow error or Heap overflow error.	{Either of these errors indicates that there is not enough memory available to run CHRRNAV. Too many device drivers and TSR's (terminate and stay resident programs) loaded in CONFIG.SYS and AUTOEXEC.BAT can cause this error. Poor memory management or not enough RAM can also cause this.}
204	Invalid pointer operation.	{You should never get this}
205	Floating point overflow.	{You should never get this}
206	Floating point underflow.	{You should never get this}
207	Invalid floating point operation.	{You should never get this}

Go to Table of Contents

Any Word in Context Index	Anyword.txt
Codebook	Codebook.txt
Key Word in Context Index	Keyword.txt
Question Name List	Question-name.txt
Record Number Index	Record.txt
Variable Name List	Varname.txt
Year Index	Year.txt