README.604 January 30, 2001 Epi Info 6.04d README --------------------- CONTENTS -------- 1. What's new in Epi Info, Version 6.04d? 2. What's new in Epi Info, Version 6.04c? 3. What's new in Epi Info, Version 6.04b? 4. What's new in Epi Info, Version 6.04a? 5. What's new in Epi Info, Version 6.04? 6. What's new in Epi Info, Version 6.03? 7. General Information 8. Technical Support 9. How to get Epi Info and Epi Map 10. Disk Space and Installation of Epi Info 6 11. Using Epi Info on a Local Area Network 12. Printing the Electronic Manual 13. Specific Information 14. Translations 1. What's new in Epi Info, Version 6.04d? ----------------------------------------- Epi Info 6.04d represents a fairly minor upgrade of Epi Info 6.04c (released as a patch to version 6.04b and titled "Version 6.04b to c Upgrade - October 1997"). Primarily, a small number of bugs were fixed in ENTER/ENTERX. EPI6.EXE/EPIGLUE.EXE/NETSS.EXE and CSAMPLE.EXE. Specific changes/bug fixes are as follows: A. ENTER/ENTERX - Both programs failed when executed on PCs running at 900 MHZ and higher. This was a TurboPower problem that has been fixed. B. EPI6.EXE/EPIGLUE.EXE/NETSS.EXE - The menu program would not open a file for editing (F3) on machines running faster than 200 MHZ with a CD-ROM drive. This has been fixed. C. CSAMPLE.EXE - Fixed a bug that incorrectly computed the standard error for PSUs (or strata thereof) that had no valid values. 2. What's new in Epi Info, Version 6.04c? ---------------------------------------- In Epi Info 6.04c (released as a patch to version 6.04b and titled "Version 6.04b to c Upgrade - October 1997"), support for four-digit-years has been enhanced in EPED, ENTER/ENTERX, ANALYSIS, EXPORT and MERGE (thus, addressing the "year-2000" problem). Bugs were removed from EPITABLE.EXE and EPINUT.EXE. CONFIG.EPI has been added. Specific changes are as follows: A. EPED - A 4-digit year format was added to the available formats on the QUESTIONS option. B. ENTER/ENTERX - Fixed a bug in validate mode when one field is blank. Added more support for 4-digit years (YYYY) and dates beyond 1999. Dates can be changed between 2-digit year format (YY) and 4-digit (YYYY) by revising the .QES file and revising the structure of the .REC file. C. ANALYSIS - (i) ANALYSIS.EXE now contains what was, in previous releases, stored in ANALYSIS.OVR. (ii) Changes were made to support "European" SYSTEMDATE, correct assignments and calculations involving European and mixed date types, to more fully support 4-digit years (YYYY) and deal properly with dates beyond 1999. (iii) Appropriate colors are now used for files written with WRITE RECFILE. (iv) Bugs were fixed in reading EPIINFO.CFG and in running CONFIG.EPI. (v) The OUTPUT command was corrected for appending to existing .REC files. D. EXPORT - Code for "dBase" files was changed to insure handling of YYYY Today fields. A post "6.04b to c" release bug that did not properly convert YYYY Today fields was fixed. E. MERGE - Added support for changing between 4-digit years (YYYY) and 2-digit years (YY) when revising a file. Note that when a 2-digit year is converted to a 4-digit year, the century (the first 2 digits of the year) used is taken from the computer's date. If that is not appropriate, the date on the computer must be changed or some other means (such as an Analysis "pgm") must be used to change the dates. At any rate, it would be wise to back up important data sets before converting dates, with Merge or any other tool. F. EPITABLE.EXE and EPINUT.EXE - (i) Problems with random number generation have been corrected. (ii) Both programs failed when executed on PCs running at 200 MHZ and higher. This was a Borland/Inprise problem that has been fixed by patching the Borland Pascal compiler. G. CONFIG.EPI - CONFIG.EPI contains sample ANALYSIS commands for configuring a printer (in this case, a Hewlett Packard-compatible laser printer). The commands in CONFIG.EPI (if present) are executed when ANALYSIS is started. H. DOMEAS/DOMEASX.EXE - Both programs failed when executed on PCs running at 200MHZ and higher. This was a Borland/Inprise problem that has been fixed by patching the Borland Pascal compiler. 3. What's new in Epi Info, Version 6.04b? ----------------------------------------- Epi Info 6.04b represents a fairly minor upgrade of Epi Info 6.04a. Primarily, a small number of bugs were fixed in ENTER/ENTERX and EPI6.EXE/EPIGLUE.EXE/NETSS.EXE. Specific changes/bug fixes are as follows: A. ENTER - (i) A bug which sometimes caused a new record to overwrite the .REC file header has been fixed. (ii) Some cases of erroneous reports of "record changed by other user,", etc., have been fixed. B. EPI6.EXE/EPIGLUE.EXE/NETSS.EXE - When the menu program shells out to run another program (e.g., ANALYSIS.EXE) a small, temporary batch file is created. In the past, the name of the batch file was constructed as follows: if EPI6.EXE was the name of the menu program, then EPI6.BAT was the name of the temporary batch file Currently, the name of the batch file is constructed as follows: if EPI6.EXE is the name of the menu program, then ~PI6.BAT is the name of the temporary batch file 4. What's new in Epi Info, Version 6.04a? ----------------------------------------- Epi Info 6.04a represents a fairly minor upgrade of Epi Info 6.04. Primarily, a small number of bugs were fixed in EPITABLE, ENTER/ENTERX, ANALYSIS, MAKELIST, EPI6.EXE/EPIGLUE.EXE/NETSS.EXE, EXPORT, and EPINUT. Specific changes/bug fixes are as follows: A. EPITABLE - (i) Runtime error 207 was caused when calculating chi-square from a table larger than 2 X 2. (ii) Runtime error 204 was caused when generating random number lists with less than 6 numbers. (iii) Generating random number lists with some numbers (e.g., 10) caused the computer to lock up. (iv) A few hot keys were fixed. B. ENTER - In some calculations, ENTER'S ^ operator produced erroneous results. Any calculations relying on the ^ operator should be performed again with the current version. (This also applies to ENTERX.) C. ANALYSIS - (i) A problem in the display of CONFIDENCE LIMITS has been fixed. (ii) The underbar character ("_") was being inadvertently allowed into variable names that were being substituted into "@" contexts. When using two (or more) "@" contexts contiguously you should separate them with the underbar character ("_"). For example, route PJ@AT_@NPERIOD.REC will route data to PJ95_1.REC when the value of AT is 95 and the value of NPERIOD is 1. (iii) An error in the help file (ANALYSIS.HLP) for the COMBINE command has been fixed. The erroneous line was: COMBINE VALUE=DIAGNOSIS TO DIAGNOSIS4 The corrected line is: COMBINE VALUE=DIAGNOSIS DIAGNOSIS1 TO DIAGNOSIS4 D. MAPTITLE.EXE (in the NETSS directory) has been replaced by MAPCFG.EXE. E. MAKELIST - A problem with file handling has been fixed. F. EPI6.EXE/EPIGLUE.EXE/NETSS.EXE - An error message was improved. NOTE: If you are running Windows 95 and receive the following error message - "File access denied. Unable to write EPI .BAT" - try the following: a: right click on the EPI6 icon; b. click on PROPERTIES; c. click on the MEMORY tab; and d. set EXPANDED MEMORY to NONE. (If you are running EPIGLUE.EXE, the error message will say "Unable to write EPIGLUE .BAT" (or "NETSS .BAT" if running NETSS.EXE).) G. EPI6.MNU - The parameter list for the IMPORT dialog box (enabled by pressing when IMPORT is highlighted under the PROGRAMS menu) was corrected from IMPORT . . . to IMPORT . . .. NOTE: The same error occurs in the April 1994 version of the Epi Info, Version 6 manual. It has been corrected in the Revision for Version 6.03, July 1995, Epi Info manual. H. EXPORT.EXE - (i) EXPORT for SPSS has been corrected to insert a RECORDS=N statement in the DATA LIST; to indicate "US dates" and "today fields" as (ADATE) and "Euro dates" as (EDATE); and "IDNUMs" as numerics; and to output only blanks for missing numerics. (ii) EXPORT for SAS has been corrected to output only blanks for missing numerics. I. EPINUT - (i) Runtime error 204 was caused when generating a random number list for 1 number. (ii) A few hot keys were fixed. 5. What's new in Epi Info, Version 6.04? ---------------------------------------- Epi Info 6.04 represents a fairly minor upgrade of Epi Info 6.03. Primarily, a small number of bugs were fixed in the menu program (EPI6.EXE, EPIGLUE.EXE and NETSS.EXE), EPED, ANALYSIS, the MANUAL-ON-A-DISK system, and HYPER. Specific changes/bug fixes are as follows: A. EPI6.EXE, EPIGLUE.EXE, and NETSS.EXE - The 6.03 versions of these files (actually, all three are copies of the same menu program file) were incompatible with VLM LAN drivers. B. EPED - (i) The EPIAID input screen did not allow more than one full screen to be entered. (ii) A blank line was inserted in a file if a carriage return fell on an even multiple of position 4096. C. ANALYSIS - (i) In the REGRESS command, the CORRELATION COEFFICIENT and 95% CONFIDENCE LIMITS were wrong when the BETA COEFFICIENT was negative. (ii) Upper ASCII characters (e.g., ) were being ignored when used in variable names that were being substituted into "@" contexts. D. MANUAL-ON-A-DISK - The last couple of pages in Chapter 39 and the Indices were not displaying properly on the screen nor were they printing properly. E. HYPER - Hyper.Exe would not run on some machines without a numeric coprocessor. 6. What's new in Epi Info, Version 6.03? ---------------------------------------- A. Extensive changes in chapters 20, 37, 38 and 39 of the manual. B. A new program ENTERX.EXE--a version of ENTER that uses memory beyond 640 K. ENTER has greatly improved multiuser data entry on local area networks. There are a number of other changes in ENTER and CHECK. C. Several statistical corrections and many bug fixes in ANALYSIS. D. Changes in CSAMPLE, VALIDATE, EXPORT, IMPORT and EPITABLE. E. A new program: MAKELIST.EXE. F. Many improvements in the MENU and HYPERTEXT systems. G. Removal of a bug in the EPIAID function of EPED. Many of these items are described in more detail in the SPECIFIC INFORMATION section. The chapters in the manual mentioned above contain new information and should be read for more detail. 7. General Information ---------------------- Version 6.00 released May 27, 1994 Version 6.01 released August 22, 1994 Version 6.02 released October 05, 1994 Version 6.03 released January 29, 1996 Version 6.04 released May 28, 1996 Version 6.04a released June 1996 Version 6.04b released January 1997 Version 6.04b to c released October 1997 Version 6.04d released January 2001 Epi Info, a series of computer programs produced by CDC and the World Health Organization provides public-domain software for word processing, database and statistics work in public health. Version 6 of Epi Info was released in May, 1994, and the latest version is available from the sources listed below and via the Internet. There are more than 40,000 documented copies of Version 5 of Epi Info in 117 countries; and Version 5 of Epi Info has been translated into 11 non English languages. Information on translations is given in the TRANSLATIONS section. Epi Info is a complete system for word processing, data entry, database management, and public health statistics for IBM-compatible microcomputers (DOS). Facilities are provided for importing and exporting a variety of file types. Although Epi Info has its own file format, dBASE files also can be analyzed directly. The entire system occupies about 8.9 megabytes with all tutorials, examples, and utilities, but the main programs occupy a total of about three megabytes. Version 6 features a configurable pull-down menu, facilities for producing and using hypertext (active text), additional statistics, and many programming improvements. Like previous versions, it runs on IBM-compatible computers under DOS, and requires only 640 K of memory (RAM), although a hard disk is recommended. The entire 600-page manual (except for one chapter of statistical background for complex sample designs) is included in hypertext format on the disks and is also available in printed form. 8. Technical Support -------------------- CDC provides funding for the Epi Info Technical Support line, currently run by TRW Inc.. The Hotline may be reached at: Phone (770) 488-8440 FAX (770) 488-8456 E-mail EpiInfo@.CDC.GOV 9. How to get Epi Info and Epi Map ---------------------------------- CDC employees may obtain Epi Info and a companion program for geographic mapping (Epi Map) from the CDC Warehouse. Persons outside CDC may obtain copies of manuals and/or programs in English from the following sources (listed in order of increasing price): Brixton Books (North America) The U.S. price is $16 740 Marigny Street plus shipping, for the New Orleans, LA 70117 manual. Disks are U.S.A. an additional $3. (504) 944-1074 FAX (504) 947-8899 and Brixton Books The price is approximately Unit K 7.50 pounds without disks Station Building Llanidloes Powys SY18 6EB Wales Phone & FAX: 44 1686 411 004 The Brixton manual omits the portion of Chapter 32 giving the equations for the statistical calculations in CSAMPLE, but this will not be essential for most users. Otherwise the USD and Brixton versions are equivalent, except for differences in price and format. Quantity discounts offered by Brixton are: Single copy orders by individuals Full price Bookshops 35% discount Health Authorities and Teaching Institutions 1-4 copies Full price 5-19 copies 35% discount 20-29 copies 40% 50-99 copies 45% 100 or more copies 50% Institutions (working) in developing countries 1-4 copies Full price 5-20 copies 40% discount More than 20 copies 50% Purchase orders are accepted for orders of $150 or more. ------------- USD, Inc. 2075-A West Park Place Stone Mountain, GA 30087 U.S.A. (770) 469-4098 FAX (770) 469-0681 The Epi Info, Version 6, programs and manual are $50 (U.S., $65 outside the U.S.), including shipping. The Epi Info manual alone is $35. The Spanish version of Epi Info 5 is $38 ($48 outside the U.S.). Quantity prices may be negotiated with Mr. Robert Crowe of USD. Epi Map may be obtained from USD for $38. ------------- INTERNET INFORMATION Epi Info and Epi Map (most recent version of each) are available on the worldwide Internet using the following access information: Site: ftp.cdc.gov; UserID: anonymous; Password: logon id Directory for Epi Info: /pub/software/epi/epiinfo Directory for Epi Map: /pub/software/epi/epimap The compressed files occupy 3-4 megabytes for each product. Files: EPI604_1.EXE About 1.3 megabytes EPI604_2.EXE About 1.3 megabytes EPI604_3.EXE About 1.3 megabytes These files are self-extracting archives. Obtain them via FTP in BINARY MODE, placing them in a directory from which you will install Epi Info (e.g., \EITEMP; do NOT use \EPI6). Execute all three .EXE files in this directory, which will produce a series of compressed files and INSTALL.EXE. Run INSTALL to install Epi Info, using the (I)nstall option. Directories called \EPI6 and \NETSS will be created and Epi Info files will be decompressed and installed. The installation files may be kept for further installations (on diskettes or on a LAN) or deleted. To create a set of diskettes of any size or density, format the equivalent of three 1.44 megabyte diskettes, and run INSTALL using the (C)opy option. This will place the appropriate number of compressed files on the diskettes and prompt you to insert each as needed. 10. Disk Space and Installation of Epi Info 6 -------------------------------------------- (Making your own Epi Info LITE) Version 5 of Epi Info consumed about 2.2 megabytes of disk space. Version 6 is a much larger system, occupying 8.3 MB for the main files, examples, and manual, with an additional 1.8 MB for the surveillance system example that is included. Version 6, like previous versions, is modular, and individual parts may be loaded and used separately. For those wishing to load parts occupying minimal disk space, the following notes may be helpful: The minimal function of data entry only can be supported by loading only the ENTER.EXE and ENTER.OVR files--275 K with a suitable .REC and .CHK files for data entry, as used in door-to-door interviewing with a laptop computer, for example. (ENTERX.EXE, RTM.EXE, and DPMI16BI.OVL (both necessary to run ENTERX.EXE) total about 467 K.) EPED, ENTER, and CHECK together form a skeletal system for creating and editing questionnaires and setting up data entry, occupying 697 K. The ANALYSIS program with its .HLP file adds another 457 K, making a very useful core system in 1.2 MB. Adding EPITABLE, IMPORT, EXPORT, MERGE, VALIDATE, STATCALC, the EPI6 menu, and a number of examples increases the total size to 3.5 MB. Adding specialized functions for nutritional anthropometry, including EPINUT, and a demonstration program for making menus called EPIGLUE brings to total size to 5.1 MB. If all the .BGI drivers for printing graphs from ANALYSIS to different printers and file formats are loaded, they occupy another 654 K. The entire Epi Info 6 manual of 600 pages, when loaded, occupies 1.15 MB. The surveillance system example (NETSS) is 1.8 MB. The total size of the \EPI6 directory, if every option is loaded, is 8.3 MB. With the \NETSS directory, the entire system occupies 10.1 MB of hard disk space. Remember, however, that most individual programs can still be run from 360 K floppy disks if necessary. 11. Using Epi Info on a Local Area Network ------------------------------------------ Information for LAN Administrators The main programs in Epi Info are LAN compatible. ENTER allows multiple users to enter data in the same file, using record- locking techniques that work through DOS and are not LAN specific. ANALYSIS (starting in Version 6.01) allows several users to read the same file and gives appropriate messages when trying to write files if this is not permitted. Epi Info may be installed on Local Area Networks (LAN's) in several different configurations, depending upon the intended use: 1. The compressed installable system, containing INSTALL.EXE and FILES01.EXE, FILES02.EXE, etc. may be placed in a LAN directory to allow users to install the system on their hard disks (using the (I)nstall option in INSTALL) or copy it to floppy disks (using the (C)opy option) for distribution to others or installation on a laptop computer. 2. The executable version of Epi Info may be installed in a LAN directory. It is important to use the INSTALL.EXE program to install the system. The main programs and examples will be installed in a directory called \EPI6. 3. Epi Info can be installed in a subdirectory that is not directly subordinate to the root directory (e.g., in N:\APPS\EPI6 and N:\APPS\NETSS). This option is allowed in INSTALL.EXE, soon after choosing the DESTINATION drive (just follow the instructions on the screen). To allow Epi Info to run properly with directories not directly off the root, a DOS ENVIRONMENT VARIABLE called EIDIR must be set to tell Epi Info where to find its directories. In this case SET EIDIR=N:\APPS will do the job. See the Sample (Novell) LAN Installation below. 4. It is possible for a user to install and run Epi Info in a writable directory on the LAN without help from the LAN administrator, although others having access to the same directory can then alter the files. LAN Notes If tutorials or examples are run from the main menu while DOS is logged to an inappropriate directory a message now suggests using the SETUP function in the TUTORIALS or EXAMPLES menu. Depending upon circumstances, this either changes the logged directory to \EPI6 or offers to copy needed files from a read-only directory on the LAN so that Tutorials and Examples will run easily. The PATH statement in AUTOEXEC.BAT must contain the location of the Epi6 directory on the LAN. This allows Epi Info to be run from the LAN without being on the user's hard disk, although the latter is also a reasonable option if there is disk space available. The programs should run faster if the system is copied to the user's own hard disk and run from there (perhaps accessing a common data file on the LAN). Programs residing only on the LAN must be loaded into RAM on the user's computer via the LAN, and this can slow things down in some cases. Sample (Novell) LAN Installation In a Novell LAN, a batch file is placed in a directory called M:\BATCH that is accessed when a user types EI6; the batch file contains the following commands: @echo off cls set eidir=n:\apps (Set an environment variable to tell Epi Info the parent directory for \EPI6 and \NETSS) map ins s6:=sys:/apps/epi6 (Set up mappings) map ins s7:=sys:/apps/netss call n:\apps\epi6\epi6.exe (Run Epi Info) map del s7: (Remove the mappings) map del s6: call m:home.bat (Go back to home) set eidir= (Erase the environment variable) echo on Although other LAN's may have different configurations or commands, perhaps this example will be helpful in setting up a smooth system for accessing Epi Info. To run the sample surveillance system contained in the NETSS directory the user must be logged into the NETSS directory, and must have write privileges. There are several choices in setting up NETSS on a LAN. Here is one solution: In the menu configuration file EPI6.MNU, in the DONETSS block, delete 'REM' from the front of lines 5, 6, and 8, making appropriate changes as needed; then add 'REM' to the front of lines 3, 4, and 9. The commands are the same as for DOS batch files. Line numbers are for this discussion only and are not in the file. 1 DoNETSS 2 BEGIN 3 cd %EIDIR%\NETSS 4 IF NOT EXIST NETSS.MNU GOTO NONETSS 5 REM n: 6 REM cd \apps\netss 7 NETSS 8 REM call home 9 cd %EIDIR%\EPI6 10 GOTO END 11 :NONETSS 12 ECHO Could not locate %EIDIR%\NETSS\NETSS.MNU menu file for NETSS. 13 ECHO Was it installed? 14 ECHO If you are running on a LAN see README.604 15 ECHO NETSS must be run from NETSS directory 16 PAUSE 17 :END 18 End 12. Printing the Electronic Manual ---------------------------------- The entire 600-page manual is accessible in electronic form through the MANUAL portion of the menu. If you do not have a printed copy (highly recommended for convenience and bedtime reading), it is possible to send the electronic manual either to a printer or to a disk file in text format, using the facilities on the menu. You will find that the manual is divided into four files, each of which must be printed separately. The four files contain the following parts: A. Title Page (p. 1) - Chapter 15; B. Chapter 16 (p. 191) - Chapter 32; C. Chapter 33 (p. 415) - Chapter 39; and D. Functional Indices (p. 577) - General Index. To print any file, do the following: 1. Choose MANUAL and then CONTENTS from the EPI6 main menu; 2. Choose any chapter in A - D above; press ; 3. Press ("Software Binder" should be at top of screen); 4. Press to print this part (A, B, C, or D) of the manual; 5. Set INCHES PER PAGE; then set STARTING PAGE NUMBER equal to the page number specified in A - D above. 6. Press again. 7. Repeat steps 1 - 6 for each of parts A - D. Be patient! The printing will take some time. When printing, be sure to give the correct STARTING PAGE NUMBER for the part you are printing so that the numbers printed at the bottom of the pages will correspond to those for the printed and electronic manuals. Page numbers are available by choosing MANUAL and then CONTENTS from the EPI6 main menu. The printed manual contains figures showing major screens and is well formatted. See GENERAL INFORMATION for sources of the printed manual and diskettes containing the programs. 13. Specific Information ------------------------ In the EPED program: ----------------------------------------------------------------------- A serious, but infrequently encountered bug in the EPIAID functions has been fixed. A memory leak prevented reading longer files correctly when user input was active. The default Right Margin setting in TXT mode has been changed to 65. In the ENTER program: ----------------------------------------------------------------------- Please read Chapter 8, page 95, in the new manual or examine that chapter in the electronic version of the manual accessed from the main Epi6 menu for a description of ENTERX, the "protected mode" or higher-memory using program that can solve your memory limitation problems, loading many related files and large .CHK files at one time. Note that use of ENTERX requires an 80286, 80386, 80486, Pentium, or compatible computer, as well as availability of memory in "protected mode". ENTERX does not use "expanded memory". If attempted use of ENTERX locks up your computer, the likely cause is an out-of-date version of memory management software (QEMM, 386MAX, etc.) on your system. Try updating your memory manager or replacing it with EMM386. Also note that use of ENTERX is advantageous only if you are unable to use ENTER because of memory limitations. Automatically incrementing fields should now work correctly with several users entering data in the same file. Various difficulties and error messages during multiuser data entry have been corrected. fields can be initialized by use of the RANGE statement in the .CHK file. For example: ID RANGE 1001 +INF END will cause the value of ID in the first record to be 1001. ENTER's set-up screen (from from the opening screen) now displays a blank default path if that is what is in EPIINFO.CFG . (In the past, a blank path led to the display of the current directory, which could leave to saving that directory as the default path.) ENTER now enforces consistent RELATE statements linking any pair of files. I.e., if two RELATE statements link the same pair of files, the statements must be governed by equal "IF" logic. The only practical way to do this is to use exactly the same statements in both locations; the preferred way is to have only one RELATE statement linking the two files. E.g., you cannot have the following two blocks of code in FILE1.CHK: FIELD1 IF DISCODE = 100 THEN RELATE ID FILE2 ENDIF END FIELD2 IF SEX = "F" THEN RELATE ID FILE2 ENDIF END You could, however, have FIELD1 IF (DISCODE = 100) OR (SEX = "F") THEN RELATE ID FILE2 ENDIF END FIELD2 IF (DISCODE = 100) OR (SEX = "F") THEN RELATE ID FILE2 ENDIF END This is inherent in ENTER's logic and has always been part of its relational structure. The first example shown describes, to ENTER, a file structure where FILE1 and FILE2 are related if and ONLY IF both DISCODE = 100 and SEX = "F". In cases where one of those criteria was false, the relation itself was false and (in the past) the related file was marked deleted. Unfortunately, enforcing this requirement will cause some existing systems not to work. The good news is that those systems (when working again) and others will no longer be subject to unexpected deletion of related records. In the CHECK program: ---------------------------------------------------------------------- If you have "core" and "related" files which share GLOBAL variables, you can now DEFINE those GLOBAL variables in each file without causing an error. It is still an error to use the same variable name for a non-GLOBAL ("local") variable as for a GLOBAL, or to define the same GLOBAL variable twice in the same file. The purpose of this change is to allow related files to declare the same GLOBAL variables as the core file so that the related files can be run without the core file but without requiring a special check file for them. E.g., in HOUSE.CHK you can have BEFORE FILE DEFINE VARADDRESS ________________________________ GLOBAL END and you can also have in PERSON.CHK BEFORE FILE DEFINE VARADDRESS ________________________________ GLOBAL END without causing an error. Note: The two definitions refer to the same variable! Only the first definition really defines the type and length of the variable. It is up to you to avoid any problems created by using the same global variable names in separate files! New "system variables" are available in check files: SYS_NEWRECORD SYS_FIELDCHANGED SYS_RESULT SYS_NEWRECORD = "Y" when the current record is the "new" record in the file. Among other things, you can use this to control what you do in a BEFORE RECORD block to avoid reinitializing fields when doing and , etc. SYS_FIELDCHANGED = "Y" when the current field has been edited. You can use this in an AFTER ENTRY block to keep from doing calculations, etc., if the current field has not been changed, such as when you are up-arrowing through the field. SYS_RESULT returns the same value as RESULT. It is provided just to be consistent with the other SYS_ variables. In the ANALYSIS program: ----------------------------------------------------------------------- A Problem with ANALYSIS' GENERATE command, where it generated the wrong number of records when over 32,767 records were specified, has been corrected. A memory leak in ANALYSIS when doing FREQ or MEANS with only one variable has been corrected. A problem where ANALYSIS could hang the machine when doing large tables has been corrected. As there is no way to predict how many unique elements will be in a table (or FREQ), there is no way to predict how much memory will be used. For this reason, memory exhaustion cannot be anticipated or corrected, and will now result in a runtime error 203. When doing large tables, the user may have the impression that the machine is hung up because there is a long delay between the time when the "percentage complete" indicator stops changing and the table is displayed. Some of the operations on large tables tend to take a while, and since the time that these operations will take cannot be calculated, there is no way to give such status indication. If you know that you are doing a long table, be patient. A problem that prevented ANALYSIS from being able to handle European dates with days higher than 12 has been corrected. Transformations between European date formats and US date formats should now be correct. A problem in ANALYSIS that caused string concatenation when only one of strings contained the missing value, to result in a missing value has been corrected. Adding a numeric to a missing numeric still results in missing. A problem which caused ANALYSIS to crash when the header of a .REC file exceeds 65526 bytes has been corrected. It has been, and still is a limitation of ANALYSIS that the header cannot contain over 65526 bytes. The correction issues a meaningful message to be issued if this limit is exceeded, and ANALYSIS will refuse to open the file. A problem that sometimes caused ANALYSIS to display garbage when the F1 key is used while displaying help, has been corrected. When the error message "Unknown token" is issued from the report writer in ANALYSIS, it now gives the token in error. A problem in ANALYSIS that produced a blank error message box to be displayed when DOS commands (ERASE, COPY, DIR) failed, has been corrected. The message given includes the actual error code returned by DOS. As there are hundreds of different error codes that can be returned by DOS, only the code is provided. Some of the more common codes are: 4 Too many open files. 5 File access denied. (The file or directory is read-only) 100 Disk read error. 101 Disk write error. (Disk is full) PLEASE NOTE: The behavior of ANALYSIS with respect to comparison of strings has been changed. In the past IF "DUMMY" = "D" would compare equal. This prevented users from being able to actually compare 2 strings for equality. But it also lead to people using this as a "feature". SELECT DISEASE = "HEP" produced "HEP A", "HEP B", "HEP NONAB", which was useful to many people. The appropriate way, in version 6 to do this is: SELECT DISEASE[1,3] = "HEP" In ANALYSIS, sorting in descending order is now supported. To cause ANALYSIS to sort in descending order, you may type SET SORT = DESCENDING and then use the SORT command. To return to normal, ascending order, type: SET SORT = ASCENDING A problem in ANALYSIS that caused European dates to be converted to US dates when SET EUROPEAN was on has been corrected. A problem in ANALYSIS which caused DEFINEd integer variables to be written to a .REC file with one decimal place has been corrected. A problem with BROWSE and UPDATE, in ANALYSIS that caused a non-existent field to be visited when using the control-right-arrow combination has been corrected. A problem in ANALYSIS that caused the R-Square statistic for linear regression to be erroneously displayed as R has been corrected. Additionally, R-Square and Adjusted R-Square for regressions with multiple independent variables is now calculated. More accurate calculation of confidence limits for linear regression has been added. A more accurate calculation of p-values from the F-distribution is now used in ANALYSIS. A new command has been added to ANALYSIS. The DESCRIBE command produces an abbreviated FREQuency report of all numeric variables. A problem that caused TABLES command to produce incorrect tables when RELATEing by non-numeric key and some tables variables were numeric has been corrected. A problem that caused ANALYSIS to occasionally drop records if the size of each record was an exact multiple of 78 has been corrected. PLEASE NOTE: This is a clarification of the method that ANALYSIS uses to locate graphics drivers. When ANALYSIS is invoked, it first searches for the display graphics driver (usually EGAVGA) in the current working directory. If it is not found there, it then tries the directory in which the ANALYSIS executable (ANALYSIS.EXE) was found. Failing that, the path specified in the DOS PATH statement is searched. It is important to note that _wherever_ the display driver is first located, ANALYSIS will expect all needed graphics drivers to be located. The additional graphics drivers that ANALYSIS needs are printer drivers ($????.BGI), and font drivers (*.CHR). If the printer drivers are not located, you will be unable to print graphics. If the font drivers cannot be located, the scaling of the graphs may be inappropriate. For these reasons, it is highly recommended that ONLY ONE COPY of the graphics drivers be present on your disk, that they all be in the same directory, and that that directory be present in the DOS PATH statement. This is a good strategy, not only for ANALYSIS and EPIMAP, but all programs that use the Borland Graphics Interface. NOTE: EGAVGA.BGI found in the EPI6 directory is NOT INTERCHANGEABLE with EGAVGA.BGI found in the Epi Map 2 directory. Setting CUMULATIVE variables to an initial value: While it is possible to set an initial value other than 0 for a CUMULATIVE variable, as in: DEFINE POPULATION CUMULATIVE 300000 the value is only set with the first pass through the data file. It is therefore better to use two statements, setting the default value on each pass through the file: DEFINE POPULATION CUMULATIVE If RECNUMBER = 1 then POPULATION = 300000 (which might be followed on the same line by ELSE POPULATION = POPULATION * 1.04 to make the population grow at a rate of 4% through a series of annual records, for example) In the CSAMPLE program: ----------------------------------------------------------------------- CSAMPLE has been modified to disallow weighting if neither stratification nor cluster is used. In the VALIDATE program: ----------------------------------------------------------------------- VALIDATE now reports duplicate keys with an improved error message "Duplicate key found at record nnn in file XXX". If VALIDATE is used with matching records enabled, the key is now shown in the output to facilitate the reconciliation of differences. In the EXPORT program: ----------------------------------------------------------------------- A problem in EXPORT to SAS that caused missing values in fixed point fields to be output as all zeros has been corrected. Missing values will now be correctly represented as "all spaces". An "INFILE CARDS PAD;" statement has been added to the SAS output of EXPORT to avert a problem that occurs in SAS for Windows, causing records to be truncated. LRECL=80 was also suggested, but produced an error when submitted to SAS for Windows. A problem that caused EXPORT to produce incorrect dBaseIV files when the dataset contained more than 128 variables has been corrected. EXPORT now exports 10-character date fields (MM/DD/YYYY) properly. A problem which caused EXPORT to comma delimited files to lock up when some fields were blank has been corrected. In the IMPORT program: ----------------------------------------------------------------------- A problem in IMPORT for "Quote and comma delimited files", which caused the last field in each record to be truncated if it was not quoted, has been fixed. Note that allowing fields not to be quoted is a new feature with version 6 of IMPORT. Of course, if a field is to contain a comma, it must be quoted. IMPORT, when importing dBase files, now imports the date as so as to retain the date in the format found in the original dBase file. In the EPITABLE program: ----------------------------------------------------------------------- The calculation of sample size for case-control studies contained a correction factor that has been removed. It now gives the same results as the Fleiss's formula and STATCALC. A difference of 1 or 2 units (on the total sample size) can be found since Epitable rounds-up sample size to the next digit (It's hard to interview a fraction of a Case or Control.) In versions 6 - 6.02, symmetric distributions failed to produce a two-tailed p-value twice the one-tailed p-value for Fisher's exact text. This has been fixed. In versions 6 - 6.02, binomial probability results were wrong for certain values of TOTAL OBSERVATIONS. This has been fixed. A New Program MAKELIST.EXE, list maker for Epi Info ----------------------------------------------------------------------- The MAKELIST.EXE utility program generates lists of variables in .REC files or of values in a specified field in a .REC file. Using the EPI6 menu program, the list can be inserted into .PGM or .CHK files for immediate use. The result is that generic .MNU files can be constructed that work with a variety of .REC files. One example, contained in the EPIGLUE demonstration menu, presents the user with a PICKLIST of all the Yes/No field names in any selected .REC file, and allows tables to be made from those selected. The newly created .PGM can include a PICKLIST generated on the fly, repeated commands on list of variables selected by type, or by name using wildcards, or a list of files that can be selected in a CHECK file during data entry. The syntax for running MAKELIST is: MAKELIST /SDNE /V=[type number] /F= /C= : DOS filters. Can be multiples e.g. *.QES *.REC /SDNE : Any of these letters or any combinations allowed. S: includes sub directories D: includes path in output N: includes name E: includes extension /V= : Outputs variable names for the given file, including extension [] can be a filter such as [CA*] for all variables starting with "CA" or a number describing the field type in an Epi Info .REC file header (See Chapter 37 in the Epi Info manual). /F= : output file. If none specified, output goes to screen /C= : file with ANALYSIS commands to include before and after the list. The command file looks like a PGM file in which a CMD= statement appears for actions to be carried out for items picked. A % in the command line stated in CMD= is replaced by the actual value of the pick. Example 1 Inserting variable names into an ANALYSIS .PGM ---------------------------------------------------------------- First we make a file of ANALYSIS-like commands. Let's call it CMD: READ OSWEGO CMD=Tables % ILL During list generation, the % will be replaced by the values of the list, in our case, by the names of all Yes/No variables of OSWEGO.REC, thus giving commands to produce tables of these variables with ILL. To do the replacement, MAKELIST is run from a block of commands in an .MNU file (See EPIGLUE.MNU for this example), and then ANALYSIS is run with the resulting .PGM file, TST.PGM. MAKELIST /V=OSWEGO.REC[5] /C=CMD /F=TST.PGM ANALYSIS TST.PGM */V=OSWEGO.REC[5] makes a list of all yes-no variables ([5]) in the * OSWEGO.REC file * We construct a file called CMD (for example) ahead of time. * /C=CMD means the command to apply to the list are found in the * file CMD (see below the content of the file) * /F=TST.PGM means that MAKELIST will construct an output file * called TST.PGM, with the list inserted. We can then run * TST.PGM from ANALYSIS using the same block of commands. The first part of TST.PGM looks like this: READ OSWEGO Tables ILL ILL Tables BAKEDHAM ILL ....... The result is a table for each Yes/No variable in OSWEGO by ILLness. Note that this result would have been achieved for ANY file called OSWEGO.REC, whether it had 1 or 100 Yes/No fields. Example 2 Inserting Filenames automatically into an ANALYSIS PICKLIST ---------------------------------------------------------------- Here is the file called SOURCE PICKLIST 10,5 CMD="%" ROUTE % "Quit" Quit END * Creates a picklist with all files with a .TXT or .DAT extension * and route the output to the selected file. The .MNU block: MAKELIST /C=SOURCE *.TXT *.DAT /DNE /F=TST.PGM ANALYSIS TST /FULL * /C=CMD (see above) * *.TXT and *.DAT are the filters to use for the list * /DNE means we want the Directory, Filename and Extension in * the output * /F=TST.PGM (as above) IF the files HELLO.TXT and ANOTHER.TXT are found in the current directory, MAKELIST generates TST.PGM as follows: PICKLIST 10,5 "C:\EPI6\HELLO.TXT" ROUTE C:\EPI6\HELLO.TXT "C:\EPI6\ANOTHER.TXT" ROUTE C:\EPI6\ANOTHER.TXT etc... "Quit" Quit END * Creates a picklist with all files with a .TXT or .DAT extension * and route the output to the selected file. Example 3 Inserting Filenames in a CHECK program ---------------------------------------------------------------- First we make FIND.CHK to go with a questionnaire called FIND.QES and its FIND.REC FIND.CHK contains the following block: CHOICE LEGAL INCLUDE INC.TXT END END A list of .BND files in two directories is generated by MAKELIST and placed in an ASCII file called INC.TXT. The following call: MAKELIST C:\EPI6\*.BND C:\EPIMAP\*.BND /DNE /F=INC.TXT ENTER FIND will run ENTER with a picklist in a .CHK file created on the fly including all .BND files in EPIMAP and EPI6 directories, assuming that the FIND.CHK file includes the INCLUDE INC.TXT statement. (6.03) In the EPI6/EPIGLUE MENU system: ----------------------------------------------------------------------- In Version 6.03, a number of changes were made to the menu (EPI6, EPIGLUE, and NETSS.EXE). All .MNU files for earlier versions should work well with version 6.03 of HYPER.EXE. Files compiled with earlier versions of HYPER can be displayed with the new menu. It is a good idea to replace any previous copies of the menu.EXE files that you may have created with copies of Version 6.03 of EPI6.EXE. A new command was created: PICKLIST, many other were expanded: VIEW, DIALOG, FILEDIALOG. New functionalities were added to the menu: BOOKMARK for the hypertext viewer, choice between 3 color palettes, and default size of hypertext windows, SETUP of Epi Info fields from the menu through a call to EPISETUP in the menu. VIEW Command VIEW accepts a new parameter /NOEDIT. When this parameter is used the file indicated after the VIEW statement is open for reading only. The user cannot edit the file. VIEW accepts the line number as a parameter. When used, this option loads the file with specified line at the top of the window. VIEW WHATEVER.TXT 200 loads the file on line 200. The Built-in Editor (reached through the FILE/EDIT menus) Alt-F8 in an editor window pops up a list of Epi Info fields that may be inserted into a questionnaire. It is the equivalent of Ctrl-Q-Q in EPED. Alt-F9 lets you enter large letters such as the ones used in the background. Two font sizes are allowed; and up to 10 characters. Ctrl-[ and Ctrl-] will type (ASCII 174) and (ASCII 175) respectively. Hypertext viewer The left and right arrows are only active if text is wider than the window. When there are a number of active hypertext points in a block and the highlighted keyword is not in the current screen, pressing the down or up arrows highlights the first or last topic in the current screen rather than zipping to the screen containing the highlighted keyword. Editing the .MNU File If the current .MNU file is edited from the menu or if %P parameters are changed, the changes take effect as soon as the file is saved. When the menu file is in an external editor, pressing on return to the menu updates the menu. A predefined menu called EPISETUP has been added to the commands allowed in an .MNU file. It works like the MENUEDIT option. EPISETUP will create a new pop-up menu with menu picks for setting colors in ENTER, default data path for ENTER and ANALYSIS and default character for ENTER fields. See the new Epi6 menu definition file as an example. Each of the four options added by a call to EPISETUP can be activated separately by using the corresponding pre-defined reserved words in a MENUITEM call: IDFIELD for the field colors IDPATH for the default data path IDCHAR for the default field character IDSETUP for printer setup Mouse The CLOSE command works with the mouse in the hypertext viewer. When a menu is displayed, double-clicking on the right mouse button pops up a "local menu" with options appropriate to the context. If no windows are active on the desktop, picks for opening a text file, a hypertext file, or creating a new text file are available. If a window is already active, menu picks for printing, saving, tiling, and cascading are added. In order to make a selection, double-click and keep the second click pressed. Then move the mouse to highlight a menu option and release. The corresponding action is carried out. To close the local menu without carrying out an action, just release the right mouse button outside the menu frame. PICKLIST Picklist is a new command that may be inserted in a command blocks in an .MNU file. Syntax: PICKLIST /VAR /ASCII /MULT A switch /MULT allows the user to enter multiple selections in a picklist statement. When used, each option can be selected using the space bar, or all options activated or deactivated by using the + or - key. When multiple selections are made, each is returned in a separate parameter %1, %2, ... A use of the SWITCH feature in DOS lets you capture as many parameters as you wish. A picklist instruction in a block of command pops up a window with a list of items that can be selected. The items can be either loaded from an Epi Info data file, or from an ASCII file. If an Epi Info data file is used, then an additional parameter should be specified. It is either the name of an existing variable in the data set, or /VAR meaning that the name of the variables are to appear in the list. If the name of a variable is specified, the various values taken by this variable will be displayed. No duplicates are allowed, and the list is sorted alphabetically. The value selected can be later accessed by using the %1 to %9 parameters. Example: DoSomething BEGIN FILEDIALOG "*.REC","Select a data file" PICKLIST %1 /VAR PICKLIST %1 %2 ECHO READ %1 >TST.PGM ECHO SELECT %2 = "%3">>TST.PGM ECHO BROWSE>>TST.PGM ANALYSIS TST END * this program displays a filedialog to select a data file, then * it lists all the variables in this data set for selection, and finally * all the values taken by the selected variable. Then it produces a TST.PGM * which is called by analysis. Entering a character will switch the cursor to the first item starting with this character. This search is not case sensitive. In Version 6.03, a bug is corrected that prevented the last item from appearing on the list. Global variables 18 predefined global variables can be referenced in command blocks by %G1 to %G9 and %P1 to %P9 parameters. The value of these global variables can be set by using a /G1 to /G9 and /P1 to /P9 switch in DIALOGS and FILEDIALOGS. Global variables are saved when leaving the program. Global variables values can be displayed in a menu by using the ^G1 to ^G9 and ^P1 to ^P9 in a MENUITEM definition. Example: In the menu: Menuitem ... Menuitem "Global variable 1^G1",DoSetVar1 Menuitem ... In the command definitions: DoSetVar1 BEGIN DIALOG "Set the default value for global variable 1","" /G1 END DoUseVar1 Begin Echo %G1 Pause End DIALOG New switches and prompt display features were added: Syntax: DIALOG "{[Prompt file]}Prompt text"{,"Filter"} {/D=} {/Gx} {/Px} The DIALOG instruction included in a block of commands pops up a window displaying a prompt string, a caption field, and 2 buttons for confirming or Canceling the entry. "Input filters" are used to specify the type of data entry expected. It can be numeric, data, or alphanumeric. If no filter is indicated, DIALOG acts as an information box with no user input. Pressing the OK button will proceed to the next command, pressing the Cancel button will interrupt the process. The value entered can be passed as a parameter to subsequent commands in the block using %1. This is comparable to the way parameters are passed to batch files in the DOS environment. The optional /D= switch, is used to specify a default value to the dialog. No consistency check with the picture format is carried out! Quotes "" are needed if spaces are used. The optional /Gx and /Px switches, in which x is 1 to 9, assigns the value returned by the dialog to the corresponding global variable. These global variables can be used in command blocks by referring to them as %G1 to %G9 and %P1 to %P9. Prompt text is displayed over the input line. Prompts can be up to 255 characters long. Two formatting codes can be inserted: /C to center the prompt, and /N to enter a carriage return. If the prompt includes a valid filename between square brackets ([]), then the corresponding file is displayed. If the file is more than 12 lines long, it is displayed in a scrolling window. Example: COMMAND2 BEGIN DIALOG "Enter year: ","##" /D=94 C:\EPI6\ENTER GEPI%1.REC END This program will prompt the user for the year to call, and then runs Epi Info Enter program on the corresponding file. If the user enter 93, then the command C:\EPI6\ENTER\GEPI93.REC will be executed. COMMAND2 BEGIN DIALOG "[ONEFILE]/cEnter your option after reading the file: ","##" /D=94 ECHO You chose %1 END Displays ONEFILE in a scrolling window and centers the prompt above the input line. EPISETUP: Adding a Setup Menu for Epi Info Default Epi Info options can be set through the menu, by adding a call to EPISETUP in the menu definition. Syntax: EPISETUP EPISETUP adds a standard set of 4 menu options that allows you to configure Epi Info field colors, character, default data path, and printer. Changes are saved in the EPIINFO.CFG file, the same file used by ENTER and ANALYSIS to retrieve default options when creating a questionnaire. Changes can thus be made either from the EPISETUP menu or from the configuration screen in the ENTER program, reached by pressing in ENTER. FILEDIALOG, FILEPARAM 2 new switches were added for FILEDIALOG and FILEPARAM: The optional /BREAK breaks the file name into its components. The path is %1, the file name %2 and the extension %3. If omitted, %1 holds the full file name including the path. The optional /Gx and /Px switches, in which x is 1 to 9, assigns the value returned by the dialog to the corresponding global variable. These global variables can be used in command blocks by referring to them as %G1 to %G9 and %P1 to %P9. PASSWORD A PASSWORD statement in a command block will prompt the user for entering a password if any has been defined using the IDPASS command. The password is saved in the configuration file after encryption. PASSWORD in a .CMD file will prompt the user for password when launching the program. Although this mechanism offers protection from casual intruders, it is quite easy to overcome by erasing or altering files and should not be thought of as a complete security system. /E:XXX Switch to Specify the Size of the DOS Environment Space DOS uses a /e:xxxx switch in the SHELL statement of the config.sys file for increasing the size of the DOS Environment Space. This switch may be useful if you get an "Out of environment space" message when running an external application or batch file. If this happens, run the menu with the switch value set to 1024 or 2048, for instance. EPIGLUE /e:2048 The command /e:2048 can be added to the macro file run at startup so that the effect is permanent (.CMD file). MENUITEM SEPARATOR MENUITEM SEPARATOR accepts a string of text as parameter. This text is displayed over the separation line. Quotes are required if leading or trailing spaces are used. Background (.SCR) files When switching to alternate menus, the background can be updated by loading a new .SCR file with the same name as the new menu block used for the menubar. EPIGLUE MENU Begin MENUITEM "Goes to new menu bar MENU1",MENU1 End MENU1 MENU Begin MENUITEM "Comes back to the main menubar",EPIGLUE End In this example, if there are two background files, called EPIGLUE.SCR and MENU1.SCR, then the background will change as the menu bar changes. The main menu needs to have the same name as the executable file (EPIGLUE.EXE in this application) in order to switch back to the default background. The HYPERTEXT (HELP) System and Hypertext Compiler, HYPER.EXE ------------------------------------------------------------------ Setting the Colors for Hypertext Displays The colors in which hypertext is displayed can be changed by pressing the or clicking on the "*" in the display. The display cycles through several different color "palettes." This is especially handy for finding a suitable display on a monochrome screen. Display palettes can also be set permanently by inserting a parameter in the file that will be compiled to produce the .HLP file. A parameter -- /PALETTE CYAN, /PALETTE BLUE, or /PALETTE GRAY -- after ".TOPIC" sets the color of the default palette for the Help file in which it occurs. Only one such parameter is allowed per file. If a palette is specified, pressing the space bar or clicking on the "*" character does not change the screen color when the file is displayed. Since this option inserts an extra byte in a file header for the compiled hypertext, files containing the PALETTE parameter are not compatible with Versions of the menu (EPI6.EXE) prior to 6.03, unless compiled with the HYPER.EXE compiler and the /OLD switch (See HYPER). Example .TOPIC /PALETTE BLUE The entire hypertext file will be displayed with a blue background and the color will not be affected by the space bar. (6.03) RETURN statement in a command block Syntax: RETURN A return statement in a command block forces the menu to return to the calling menu option after carrying out the related task instead of returning to the main top menu bar as it does by default. Example: .TOPIC WHATEVER Begin FILEDIALOG "*.*","Select a file for doing something" WHATEVER %1 RETURN End After running the WHATEVER program with the file specified in FILEDIALOG as parameter, the menu will return to the option that is associated with this command. Bookmark A bookmark is a mark in the hypertext file that allows the user to return to a given location. By default, a bookmark is inserted on the topic that was active when the window was closed. This allows the user to start later where it stopped. To return to the bookmark, you can either: * Click on the exclamation mark ! on the window frame * Insert a Go to bookmark |ONE_BOOKMARK anywhere in the file. In this case a topic definition for the bookmark needs to be entered: .TOPIC ONE_BOOKMARK=BOOKMARK BOOKMARK * Call the hypertext file through a HELP command with the /BMK switch See the EPIGLUE.HLP file, under the topic Hypertext Compiler for a discussion of added features in the compiler. Lists of TOPICs in .LST Files When compiling a text file using HYPER.EXE to produce a .HLP file, a file with the same name as the .HLP file and a .LST extension is automatically created. It contains in plain text (ASCII) format, an index of the TOPICS. In the HELP display system in EPI6.EXE and similar menus, this index can be displayed in a picklist by pressing or clicking on the question mark "?" below the hypertext window, and the user can choose a topic and display it immediately. If there is only one topic in the list, this feature is disabled. BATCH and MESSAGE topics are not included in the .LST file nor are TOPICs beginning with the underscore "_" character. This provides a way of controlling what appears in the list. The contents of the .LST file can also be used to construct a customized "index" in the actual hypertext file by judicious cutting and pasting. Default size for hypertext windows By default the size of a hypertext window is full screen. However, it can be set to a different value by editing the .BMK file with the same name as the hypertext file. This .BMK file has a SIZE statement, followed by the X and Y coordinate of the upper left corner and the lower right corner of the window. Example: SIZE=0 0 80 23 This is the default value, for full screen. SIZE=10 5 70 18 This size would leave 10 columns on the left and right of the window, and 5 lines over and below the window. Switches for the HYPER Compiler A switch has been added to the hypertext compiler: /OLD Necessary only when a .HLP file is to be displayed in a version of the EPI6.EXE menu older than Version 6.03 AND the file to be compiled contains a /PALETTE topic. It is recommended that the newer version of the menu be used so that the /PALETTE can take effect, but this method of suppressing the /PALETTE is provided so that compatibility can be maintained. The /OLD switch is not needed unless the file being compiled contains a .TOPIC /PALETTE.... Notes for "Programmer's Toolkit" and Anthropometric Calculation Example in Protected Mode: ------------------------------------------------------------------ The discussion in Ch. 39 ("The Programmer's Toolkit and the REC2QES Utility") of the Epi Info 6.03 manual includes considerations for "calling a Turbo Pascal program from ENTER" using an example program for anthropometric calculation. (Discussion of the use of the example program for such calculation is found in Ch. 23.) The discussion in Ch. 39 applies to the use of ENTER.EXE/ENTER.OVR, the Real Mode version of ENTER. Use of ENTERX.EXE, the Protected Mode version, is somewhat different. (The term ENTERX will be used here to refer to the Protected Mode version of ENTER no matter what it may have been renamed to.) If you wish only to use the example program in Protected Mode, you need to exit the EPI6 menu and execute the program MEASUREX.BAT directly. (Alternatively, you or someone else can modify the EPI6 menu to run the Nutritional Anthropometry examples from the menu.) E.g.: C:\EPI6> MEASUREX If you want to use the example program as a model of interfacing external programs (such as DOMEASX.EXE, in the example) to ENTERX, here are the things you should note: 1) Unlike Real Mode, this Protected Mode approach does NOT use "TSRs". Instead, the external program itself must be a Protected Mode application which executes ENTERX. There is no need for MARK and REMOVE in this Protected Mode approach. 2) As a consequence of 1), only one such external program can be active at a time. We view this as a minor issue at present, being unaware of anyone who is using multiple TSRs in interfacing to ENTER. Also, the capability of passing numeric codes in the ENTER/CHECK CALL command allows one external program to perform a variety of functions by testing the value of the passed code. 3) The Protected Mode interface was developed for Borland Pascal and its 286 DOS Extender. Although it may be possible to interface to ENTERX with other compilers and/or DOS extenders, no others will be supported by the Epi Info Support or Programming Teams. 14. Translations ---------------- Translations of Epi Info and/or Epi Map: TRANSLATOR COLLABORATOR/SPONSOR/DISTRIBUTOR ---------------------------------------------------------------------------- ARABIC ------ Dr. Samy Sidky USD, Inc. P.O. Box 1784 2075 A West Park Place Cairo, Egypt 11511 Stone Mountain, GA 30087 U.S.A. Tel: 20 2 418 5746 Tel: (770) 469-4098 Fax: 20 2 418 2245 Fax: (770) 469-0681 20 2 418 2246 or C/O MEMCO International P.O. Box 888696 Norcross, GA 30356 U.S.A. Tel: (404) 901-9604 (Voice and FAX) CHINESE ------- Dr. Pihuan Jin, Professor Dr. Donald DeSavigny Department of Health Statistics Health Sciences Division Shanghai Medical University International Development School of Public Health Research Center 138 Yi Xue Yuan Road 8500 Ottawa, Canada K1G3H9 Shanghai 200032 Tel: 613-236-7230 People's Republic of China Tel: 86 17 4311900 ext 86 21 4330543 CHINESE (Continued) ------------------- Dr. Wang Gong Hao and Dr. He Wu Center for Computer Science and Health Statistics Chinese Academy of Preventive Medicine 10 Tian Tan Xi Li Beijing 100050 People's Republic of China Tel: 86 17 012210 Fax: 86 17 015342 E-mail: p2149715@vmsuser.acsu.unsw.EDU.AU CZECH--Manual ------------- Ing. Zdenek Roth, CSc. Dept. of Mathematical Statistics and Programming National Institute of Public Health Srobarova 48 100 42 Praha 10 Czechoslovakia Fax: 010 42 2 73 65 80 FRENCH ------ Drs. Bernard Junod et Robert Freund Editions ENSP Dpartement Mthodes, Sant et Population Ecole Nationale de la Sant Publique Ecole Nationale de la Sant Publique Avenue du Professeur-Lon-Bernard Avenue du Professeur-Lon-Bernard 35043 RENNES Cedex, FRANCE 35043 Rennes Cedex FRANCE Tel: 33 02 99 28 28 59 Fax: 33 02 99 28 28 28 or Dr. Denis Coulombier E-mail: coulombi@b3e.jussieu.fr GERMAN--Manual -------------- Dr. Med. Gnter Pfaff, M.P.H. Landesgesundheitsant Baden-Wrttemberg Abteilung Epidemiologie und Gesundheitsberichterstattung Postfach 10 29 74 D-70025 Stuttgart Fax: 49 (711) 202-3399 HUNGARIAN--Manual ----------------- Dr. Ilona Straub Head, Department of Epidemiology National Institute of Hygiene Budapest IX., Gyli t 2-6 H 1966 Tel: 36 1 2151792 Fax: 36 1 2150148 INDONESIAN--Teaching Manual --------------------------- Dr. Pandu Riono and Dr. Iwan Ariawan University of Indonesia School of Public Health Department of Population Studies and Biostatistics Kamput Universitas Indonesia Depok, Indonesia Tel: 021 727-0014 0037 Fax: 021 727-0153 Programs and Manual Dr. Michael J. Dibley and Dr. Hari Kusnanto Bulaksumur D-4 Yogyakarta 55281 Indonesia Tel: 274 65076 ITALIAN--Teaching Manual and Manual on Disk ------------------------------------------- Francesco Violante M.D. Policlinico Sant'Orsola Malpighi Servizio di Medicina del Lavoro (Sant'Orsola Malpighi Hospital, Occupational Health Service) via Palagi 9, 40138 Bologna, ITALY Tel: 39 51 636 2609 Fax: 39 51 306 673 E-mail: violante@bo.nettuno.it Technical Support Marco Biocca M.D. Centro di Documentazione per la Salute (Health Documentation Center) via Triachini 17, 40138 Bologna Tel: 39 51 395 311 Fax: 39 51 392 416 or Pasquale Falasca M.D. Tel: 39 544 409 141 Fax: 39 544 409 063 PORTUGUESE--Manual ------------------ Dr. Jose Cassio De Moraes, Professor Department of Social Medicine (Mediana Social) School of Medicine of Santa Casa de Sao Paulo R. Cesario Motta 12, Sao Paulo Brasil Tel: 005511 2207122 R580 005511 2773882 RUSSIAN ------- Produced under contract to CDC, Dr. Scott McNabb Atlanta by: Jaspan Associates, CDC/EPO Inc. 1600 Clifton Rd. MS A-19 Atlanta, GA 30333 USA Tel: (404) 639-4362 Fax: (404) 639-1513 E-mail: sym3@cdc.gov SPANISH ------- Juan Carlos Fernandez-Merino Pan American Health Organization Sistema de Vigilancia Epidemiologia Distributed by: de Andalucia USD, Inc. Direccion General de Salud Publica y 2075 A West Park Place Participacin Stone Mountain, GA 30087 U.S.A. Consejeria del Salud. Junta de Tel: (404) 469-4098 Andalucia Fax: (404) 469-0681 Av. de la Innovacion Sevilla 41071 Spain Tel: 34 5 4558100 Fax: 34 5 4389506 E-mail: JUCAR@CICA.ES VIETNAMESE ---------- Dr. Michael Linnan CDC/IHPO Tel: (770) 488-1097 E-mail: mjl1@cdc.gov hanoi!mlinhsph@netnam.org.vn@x postbox.anu.edu.au ______________ End of README _______________