Anda di halaman 1dari 40

EPI INFO VERSION 3.5.

4
READ ME FILE
04/04/2012

TABLE OF CONTENTS
-----------------

INTRODUCTION
WHAT'S NEW IN 3.5.4
END-USER SYSTEM REQUIREMENTS
INSTALLING EPI INFO 3.5.4
SPECIFIC CHANGES IN EPI INFO 3.5.4
KNOWN ISSUES IN EPI INFO 3.5.4
WHAT'S COMING WITH EPI INFO 7 (AT THE END OF THIS DOCUMENT)

INTRODUCTION
------------

Epi Info 3.5.4 is an upgrade release to version 3.5.3 of Epi Info. The latest
version of the Epi Info 3 series was enhanced to include an updated component for
calculating z-score.
It also contains fixes to known bugs and issues. This document summarizes the known
bugs, workarounds, and other important issues to be aware of in this release.

WHATS NEW IN 3.5.4


------------------

1. Updated Windows Scripting Component (.WSC) for calculating z-score.


2. Updated OpenEpi local files.
3. Enhanced installation for Windows 7 Operating Systems (separate installation of
DHTML Editing Control is no longer necessary).

(A detailed list of individual bug fixes, changes, and enhancements is given in the
section �Changes in Epi Info 3.5.4� below.)

END-USER SYSTEM REQUIREMENTS


----------------------------

Note To System Administrators (and others):


The Microsoft Access files (MDBs) in Epi Info, including the sample databases
require read/write privileges. Epi Info EXE files can be run from a read-only
system, but the MDB's and the configuration file, EpiInfo.INI must be in a writable
directory. Settings are provided in the Menu for "Working Directory" and "INI File
Directory" ; these settings are stored in the Windows registry, and can be changed
from the menu with administrative privileges prior to using the system with more
limited access.
In a network system, such as a computer laboratory, Epi Info must be installed on
each local computer. Although Epi Info itself does not run from a server, it can
be installed from a server, or installed on the server or one local machine and
then imaged to the others. Epi Info databases, however, can be accessed by more
than one user simultaneously on a server, allowing several users to enter data in
the same file. Automatic record locking allows this to happen in an orderly way.
This feature is useful for team data entry, but less so in a classroom situation.

=== WINDOWS 98, NT 4.0, 2000, REQUIREMENTS ===


- A 200-megahertz (MHz) processor (Pentium compatible or greater) is recommended
but not required.

- 32 MB of Random Access Memory. More RAM: 64 MB for Windows NT 4.0 and 2000.

- At least 260 megabytes of free hard disk space to install; 130 megabytes after
installation.

- For Epi Info 7, the Microsoft .Net Framework Version 3.5 or later is required.

=== WINDOWS XP, Vista, and WINDOWS 7 REQUIREMENTS ===

- Pentium 300 megahertz (MHz) processor or faster (300 MHz is recommended).

- At least 260 megabytes of free hard disk space to install; 130 megabytes after
installation.

INSTALLING EPI INFO 3.5.4


-------------------------

To install Epi Info, administrative or power user rights to the computer are
required.

- Vista Users only. Before installing Epi Info 3.5.4, remove any prior versions of
Epi Info for Windows (DOS versions okay).

- Users must be able to read and write to the Epi Info installation directory.

- Epi info should be installed locally on each user's machine. Multiple users
sharing the same mechanism can share the same installation of Epi Info.

- Installation to a network drive is not supported.

- In order to run the Epi Report module, Internet Explorer 5.0 or above is
required. The Print Preview feature of Epi Report requires Internet Explorer 5.5 or
above.

Special Instructions for Windows XP

- Window XP Service Pack 3 is required


Download the Windows XP Service Pack 3 at
http://www.microsoft.com/downloads/details.aspx?FamilyID=2fcde6ce-b5fb-4488-
8c50-fe22559d164e&DisplayLang=en

Special Instructions for Windows Vista and Windows 7

- Before installing Epi Info 3.5.4, remove any prior versions of Epi Info for
Windows (DOS versions okay).

- The DHTLM Editing Control for Applications must be installed.


Download the DHTML Editing Control for Applications at
http://www.microsoft.com/downloads/details.aspx?FamilyID=B769A4B8-48ED-41A1-
8095-5A086D1937CB&displaylang=en

EPI INFO VERSION 3.5.3


READ ME FILE
01/26/2011

CHANGES IN EPI INFO 3.5.2 / 3.5.3


---------------------------------
ENTER
-----
I353-1 The Enter tool is corrected to preserve edits to Text type fields when using
the mouse to navigate between records rather than Tab or Enter.

EPI INFO VERSION 3.5.2


READ ME FILE
12/17/2010

CHANGES IN EPI INFO 3.5.2


-------------------------
GENERAL
-------
I352-51/69 For Epi Info 3.5.2, the online help file, eihelp.chm, has been updated
with various edits and corrections, including updates for the new version.

I352-20 Clicking the �WebBoard� link on the Epi Info website did not work.
This has been corrected to direct users to the new forum site on phConnect:
http://www.phConnect.org/group/epiinfo/forum

I352-67 General testing and updates required for compatibility with Vista and
Windows 7 operating systems.
Most, if not all Vista and Windows 7 issues have been addressed in Epi Info
3.5.2. Please email a report of any outstanding issues you discover to the Epi Info
Help Desk at EpiInfo@cdc.gov.

MENU
----
I352-47 Include the OpenEpi Calculators as an alternative to EpiInfo�s DOS based
StatCalc utility.
Added a new MENUITEM under the Utilities Pop-Up on the EpiInfo.mnu file to show
�OpenEpi Calculators�.

MAKEVIEW
--------
I352-04 User supplied data table names may result in errors if names are invalid or
reserved words.
In Epi Info 3.5.2, validation is applied to data table names matching the rules
for valid View names.

I352-19 Help|Contents on the menu bar resulted in a "cannot display webpage" error.

This has been corrected to display the "Introduction to MakeView" page.

I352-48 Update the standardized vocabulary database, PHINVS.mdb.


This version includes a more complete version of the available vocabulary and
has been pre-installed in MakeView for immediate use.

I352- MakeView was inconsistently spelled throughout the tool.


This has been corrected to be consistently spelled as one word with a capital V.

I352-21 MakeView Check Code Editor command buttons are in correctly shown on the
editor tab control.
Buttons on the editor tab control are now aligned with standards.
I352-23 Focus for controls on the user dialog for the DIALOG command are in a non-
standard sequence. The dialog has been standardized.

I352-24 Focus for controls on the user dialog for the ASSIGN command are in a non-
standard sequence. The dialog has been standardized.

I352-39 Customized tab order is automatically reset to the default order whenever a
field is moved even slightly. This causes a loss of the user�s effort to designate
a custom order of field entry.
The �Order of Entry� dialog has been changed to add a check box to �Always Use
Automatic Tab Ordering�. When unchecked, as when customization is detected, the
custom tab order is preserved when fields on the View are moved.

I352-66 In previous versions, the NEWRECORD dialog box contained incorrect text in
the title bar.
This has been corrected to show "NEWRECORD" in the title bar.

I352-75 The dialog for the RECODE command is incompletely translated when using
non-English languages.
This has been corrected to allow for complete translation. The dialog and some
controls were widened to accommodate words and phrases that are up to 1.5 times
longer when translated.

ENTER
-----
I352-06 A relate button prompt having an apostrophes results in errors when running
in Enter.
In Epi Info 3.5.2, the issue with the relate button has been corrected to use
the correct field name of the relate button rather than the relate button's prompt.

ANALYSIS
--------
I352-15 When entering recode requirements into the dialog for the RECODE command,
if zero is entered in the �To� column, the resulting command shows missing (.)
instead.
For Epi Info 3.5.2, the resulting RECODE command correctly shows a zero when zero
is specified in the RECODE dialog.

I352-16 On Vista and Windows 7 operating systems, when Epi Map is called from an
Analysis command, the Epi Map Incomplete Join dialog appears in the background and
cannot be clicked causing Analysis to appear to freeze.
The Epi Map Incomplete Join dialog now has an icon on the Task Bar and the main
Analysis tool is minimized to display the dialog, then restored when Epi Map is
closed.

I352-17 On Vista and Windows 7 operating systems, the EpiGraph window was not
brought to the front when creating a graph or chart.
For Epi Info 3.5.2, the parent Analysis window is minimized in order to show the
EpiGraph window, then restored when EpiGraph is closed.

I352-18 The FileSpec dialog partially displayed an incorrect control when TEXT is
specified as the Data Source.
The form was corrected to show only the relevant controls.

I352-34 On Vista and Windows 7 operating systems, the EpiGraph window crashes on
an attempt to export the graph to a file.
EpiGraph has been corrected to allow a graph or chart to successfully export to
a file.
I352-59 If a user has not applied a change to the user dialog for the SUMMARIZE
command before clicking �OK�, the dialog requires the user to first click �Apply�,
then click �OK�, when a simple �OK� click should be sufficient.
This has been corrected so that the user needs only to click �OK�. The validation
checking for �Apply� is performed, and if valid, the settings are accepted and the
dialog closed.

EPI REPORT
----------
I352-80 Vista and Windows 7 operating systems do not include the DHTML Editing
Control which is a required component for Epi Report. This control used to be
included with earlier versions of Windows.
For Epi Info 3.5.2, the DHTML Editing Control setup package is provided for Vista
and Windows 7 operating machines. The control's setup must be run separately
following the Epi Info installation.

Epi Lock
--------
I352-78 When selecting to delete the original file following encryption, Epi Lock
performs a lengthy byte-by-byte file comparison prior to performing an inefficient
method for wipe-delete of the source files.
Epi Lock performance was improved by using a more efficient binary file
comparison program and by optimizing the wipe-delete method.

EPI INFO VERSION 3.5.1


READ ME FILE
08/11/2008

CHANGES IN EPI INFO 3.5.1


-------------------------

The following modifications have been made to the application and are included with
this release:

GENERAL
-------

- Microsoft Windows Vista is supported. Please see the Installing Epi Info 3.5.1
section and the "Special Instructions for Windows Vista" for specific requirements.

- The previous version was not compatible with right-to-left reading languages. Epi
Info 3.5.1 is now compatible with these languages.

EPI REPORT
----------

- In the previous version, a problem was discovered where the system would generate
an error in Epi Report if you tried to insert an XML file with more than one
command. This has been fixed to allow XML files with multiple commands to be
inserted in Epi Report.

- In the previous version, a problem was discovered where Epi Report would cause an
error when switching between the report generate mode and the report design mode
with one line listing. This has been fixed to prevent this error.
ENTER
----------

- When a user exceeds the maximum record size on the first page of a multipage
table and attempts to advance to the second page, the data entered on the first
page shifts to the second page. A warning message now appears when the user exceeds
the maximum record size.

KNOWN ISSUES IN EPI INFO 3.5.1


------------------------------

The following issues will be fixed in future releases:

- When a user enters invalid Check Code in MakeView an error message displays and
the user is no longer allowed to enter Check Code. The user must restart the
MakeView Program Editor.

ReadMe (Epi Info, Version 3.5, June 9, 2008)

CHANGES IN EPI INFO 3.5


-------------------------

The following modifications have been made to the application and are included with
this release:

MAKEVIEW
--------

-The latest version of the Epi Info software was enhanced to include a new standard
vocabulary feature. The new feature required modifications to MakeView to allow the
use of standardized vocabularies, such as the Public Health Information Network
(PHIN) Vocabulary. MakeView was modified in order to enable the use and exchange
of consistent information among public health partners. This feature will enhance
Public Health by promoting the use of vocabularies that are aligned with various
healthcare industry standards such as ICD-0, HL7, and FIPS.

-In the previous version 3.4.3 a problem was discovered where the system in the
MakeView Check Code editor was replacing the return key with an unknown character
which causes a syntax error for If/Then/Else statements. Now the system correctly
displays the If/Then/Else statements and executes command without error.

ReadMe (Epi Info, Version 3.4.2, October 22, 2007)

CHANGES IN EPI INFO 3.4.2


-------------------------
The following modifications have been made to the application and are included with
this release:

ANALYSIS
--------

- In previous versions, when attempting to merge tables, any record with a null
value in the merge key stopped the merge process. This problem has been fixed so
that the merge will not stop, but a brief message displays that a null value was
detected.

- In previous versions, a fatal error would close Analysis when "Run This Command"
was clicked with only one new line entered in the program editor without a carriage
return. Now, Analysis recognizes the line without a fatal error.

- In previous versions, the Analysis GRAPH command did not display the correct X
and Y axis label values. Now, Epi Graph displays the correct names for each axis.

- In previous versions, an IF/THEN condition could not detect when a variable was
equal to a null value as in �IF var1=(.) THEN�. The IF condition was never true
and the command block was never executed even when the variable had a missing
value. Now, the IF command will return true when a variable with a null value is
compared equal to missing.

- In previous versions, fields having both a format string and contain the value
zero (0) are displayed or treated as null or blank in Analysis. Now, fields
containing the value zero are treated as zero regardless of the field�s format
string.

- In version 3.4, date functions raised an error message when passed a variable
with no data type or value. Now, date functions passed a variable with no type or
value always returns a null value (missing) with no error message.

COMMON
------

- In previous versions, the "@@" replacement operator returned a wrong value of a


dot/period (".") when used with a permanent variable that had a null value. This
problem has been fixed.
- In previous versions, the output of the GetPath command was missing a required
terminating backslash. Now, the problem is fixed to include the required backslash.

DATA COMPARE
------------

- In previous versions, for a View with over 200 fields, the "Fields to Compare"
section of the Wizard would not retain the selected fields� check box status
requiring the fields to be selected again. Now, the check box status is retained.

ENTER
-----

- In previous versions, an error was raised when moving from a parent View that has
Check Code assigning a value to a global variable to a RELATEd View with Check Code
using the global variable. This problem has been fixed.

- In previous versions, when commenting (*) a Check Code line that includes an
apostrophe, a syntax error was raised even though the line is commented. Now,
syntax checking does not occur on commented lines.

EPI GRAPH
---------

- In the previous versions, the point label orientation appeared to point in the
wrong direction. Now, the problem is fixed so the Graph pointer no longer points in
the wrong direction.

EPI MAP
-------

- In previous versions, an error occurred if the �Records for Features� button was
selected in Epi Map with no related database. Now, the �Records for Features�
button is disabled until the requirements to use the feature are met.

- In previous versions, an error occurred when the first row of the Epi Map
choropleth color gradient range was selected in the Map Manager. Now, these system
generated values are disabled.

MAKEVIEW
--------

- In previous versions, an error was raised when attempting to add Check Code to a
field with a field name beginning with the word �Page�. Now, this error is fixed.

- In previous versions, a View became corrupt when importing a .REC (EPI6) file if
there was a question mark "?" at the end of the prompt. Now, the system will
process any REC file that contains a �?� without error.

- In previous versions, an error was raised when creating a new field with a prompt
that includes an apostrophe. This has been fixed so prompts can include one or
more apostrophes without an error.

- In previous versions, in MakeView and Analysis when the DIALOG command is used
with "list of values", the data type of the selected input variable was wrong and
after selecting the input variable, variables of the wrong data type were shown in
"Show Variable" list. This problem has been fixed to show the correct data type of
the selected input variable and the correct �Show Variable� list.

- In previous versions, the Check Code Editor allowed the user to switch variables
without saving changes or asking the user to save. Now, the Check Code Editor asks
the user to save or discard any changes before switching variables.

- In previous versions, an error occurred in the Check Code Editor when a long
command line became wrapped across more than one line. Now, long command lines are
interpreted correctly.

MAKEVIEW/ENTER
--------------

- In previous versions, when the language is changed to a non-English language,


MakeView and Enter sometimes revert to English. The problem has been fixed to
retain the language setting.

MENU
---------

- In previous versions, the REPLACE command did not work with a string that
contained a comma. Now, a string with a comma is allowed in menu dialog boxes
without error.

=========================

README (EPI INFO, Version 3.4.1, July 9, 2007)

The following modifications have been made to the application and are included with
this release:

ANALYSIS
--------

- In the previous version, long lines in Analysis PGM Editor caused code not to
run. This has been fixed.

- In the previous version, when a default language was set to Arabic, the English
PGM would display right justified. This problem has been fixed with a new
controller that will allow the language to be read from left to right.

- In the previous version, Analysis displayed a gray box when handling wide table
issues. This problem has been fixed.

- The MAKE VIEW/ANALYSIS DIALOG command generator selects incorrect type for typed
variables. In the Dialog command When a Date variable is selected text is displayed
in the "variable Type" combo box. This problem has been fixed.

- In the previous version, user will receive runtime error when running several
table commands in Analysis and then maximize the browser window of .PGM. You can
not minimize or move form while browser is maximized. This has been fixed.

COMMON
------

- In the previous version, The Menu DIALOG command buttons did not display buttons
if the command read as "BUTTONS =" with a space before the equal '=' sign will
display text field instead of buttons. This has been fixed.

ENTER
-----

- In the previous version, the FIND functionality was not capable of including
deleted records. This has been changed to allow user to change settings in Analysis
SET command and then return to Enter module and select include all deleted records.

EPI MAP
-------
- In the previous version, user could not create a new Merged Layer. This has been
fixed.

- In previous versions, a runtime error was raised when the "Records for Feature"
button was clicked for a map with no related data. Now, the 'Records for Feature'
button is disabled for a map with no related data.

- In previous versions, an error occurred when the first row of the Epi Map
choropleth color gradient range was selected in the Map Manager. Now, these system
generated values are disabled.

EPI REPORT
----------

- In the previous version, the PrintRep program continues to run in the background
after Epi Report has been closed. This problem has been fixed.

MAKE VIEW/ENTER
---------------

- In the previous version, Make View was allowing .CHK file to be saved with an un-
terminated string (an open quote and no closed quote), but in Enter the program
detected the un-terminated string and locked up. This problem has been fixed to
allow the program to check for double quotes (") in a string.

README (EPI INFO, Version 3.4, April 30, 2007)

The following modifications have been made to the application and are included with
this release:

Analysis
--------

- You can now run a report from Analysis and save the output to a particular file.

- In previous versions, Analysis could perform statistics only on individual fields


and variables, it is now possible to define group variables in Analysis and use
them when calling statistical commands.

- In previous versions, the WRITE command would give an error message for all file
types if there were no records selected. Now, if the output is an Epi 6 REC file
or a Jet table, the WRITE command will write a table/file with variable information
but no data.

- It is now possible for the user to specify the year and century used when
importing Epi 6 files.

- In previous versions, generation of summary data from a stratified TABLES command


could produce errors with no output. This has been fixed.

- In previous versions, due to incompatibilities with MDAC versions 2.7 and higher,
Complex Sample routines did not return an output. This has been fixed.

- In previous versions, the 'Decimal' data type was not supported. Use 'Double' or
'Single' instead. If a table is found to contain 'Decimal' data type fields,
Analysis will convert them to Double.

- In previous versions, you could not pass the X-axis and Y-axis labels from the
GRAPH command. This has been fixed.

- In previous versions, invalid expressions in assign statements resulted in errors


when an assigned variable is used in commands. This has been fixed.

- Analysis now gives a warning message along with chi-squared results when an
expected cell frequency is five or less.

- In previous versions, Analysis created instances of the Epi Report and Epi Map on
startup. This has been fixed.

- In previous versions, when the logistic regression algorithm failed, an error


message was displayed along with the results from the previous regression. Only the
error message is displayed.

- In previous versions, a QUIT command in a true branch of an IF command not


dependent on a field or standard variable would not prevent the execution of
commands in a false branch. This has been fixed.

- The MAP command now has the ability apply a multiplier when calculating rates.

- In previous versions, errors in the EXECUTE command caused a system error


message. Now they cause a custom error message.

- In previous versions, MEANS produced no XML output for any stratum except the
first. This has been fixed.

- In previous versions, when using the FREQ, TABLES or MEANS commands with field
names over 47 characters caused an error. This has been fixed.

- In previous versions, stored programs could be created with names different from
others solely by having leading or trailing spaces. Now existing names will be
treated the same even if they have a different number of leading or trailing
spaces. New stored programs cannot be created with names that have leading or
trailing spaces, or have spaces or special characters other than an underscore and
dollar sign in their names.

- In previous versions, defined Yes-No type variables were not listed in HTML. This
has been fixed.

- In previous versions, linear regression did not reject cases with missing values
in the first independent variable. This has been fixed.

- If a current record set has missing values for a build key when using the MERGE
command, a warning message should display.

- In previous versions, the LIST GRIDTABLE and LIST UPDATE in a non-English


operating system would display an ISAM error. This has been fixed to display data
in the grids.

- A valid value in the Data Format combo box is required on the RELATE gen screen.
- The SELECT command shall choose records from the current data source that will be
processed based on a logical expression without an error even when the logical
expression contains a field variable or a standard defined variable that has been
assigned a constant value.

- A new menu item "Insert Command at Cursor" was created under the EDIT menu. The
menu is checkable. When it is checked, the new created command will be inserted at
the cursor position. The default is unchecked.

- The grid used in LIST GRIDTABLE and LIST UPDATE now supports navigation keys.

- In previous versions, you could run multiple instances of Analysis at the same
time with possible bad consequences. This has been fixed.

- In previous versions, pressing the Clear button on the command generation screens
for LIST, TABLES, MEANS and FREQ did not clear the 'All Except' checkbox. This has
been fixed.

- In previous versions, when generating a graph command, it was possible to enter a


non-integer value for the number of graphs across or down a page, or to enter a
number beyond the capability of the program to display. This resulted in an error
message when the user clicked OK. You can not enter non-integer values.

- In previous versions, when a current MERGE record has missing values for a Build
Key, a gray box was displayed. The system will now display an error message.

Common
------

- In previous versions, the Epi 6 Import routine changed REC file fields with
invalid values to missing, or skipped invalid records, without warning the user.
Now, if the REC file contains invalid data, a message is displayed.

- A new form of the DIALOG command has been added to display a file selection
dialog for open/read and save/write in Analysis and Make View/Enter.

- The DIALOG command can now accept input that is only a valid date or time value,
or only a numeric value in a particular format.

- In previous versions, the font of text in the program editor via the menu could
not be set. This has been fixed.

- In previous versions, the style and color of the default editor font could not be
saved. This has been fixed.

- In previous versions, the command generation screens for ASSIGN, DELETE RECS,
SELECT, IF, and GENERATE RELATION (relate and merge), when typing a variable name
into a variable selection combo box, the variable name would appear twice. This
has been fixed.

- In previous versions, when the DIALOG command referenced a non-existent table or


field or attempted to set an undefined variable or variable of the wrong type, no
error message was displayed. This has been fixed.

- In recent versions, it was not possible to use the �+� operator to count the
number of checkboxes that were checked. This has been fixed.
- In previous versions, the EXECUTE command sometimes ran modally and sometimes
non-modally. When the user chooses the EXECUTE command, it will run either modally
or non-modally.

- The editor control has been upgraded and various changes have been made to
improve the operation of the program editor in Make View and Analysis.

- �TerEdit� function keys should be disabled or put in a menu.

- Epi Info now accepts the ISO date format when enclosed in pipes ("|"), such as |
2007/01/02|

Compact
-------

- In previous versions, the Compact source file name could not be changed to the
default destination file name. This has been fixed.

Data Comp
---------

- In previous versions, the table link was broken when using a database table name
that is case sensitive. This has been fixed.

- A new menu item, HTML has been added to the File menu that allows HTML reports to
be reviewed in Internet Explorer.

- In previous versions, the Data Compare wizard page only translated one time. This
has been fixed.

- The AutoNumber field can be selected as a match key field if the Standard Table
is selected as Type of Table from the Wizard page Step 1.

Enter
-----

- In previous versions, the Enter module in full screen mode changed the page when
a user entered an invalid value for comment legal value. The system did not save
the invalid value, but went to the page intended without displaying an error
message. This has been changed to display an error message and to stay on the same
page until the value is corrected.

- In previous versions, when entering data into a DATETIME field, a 'PM' entry is
capitalized as 'AM'. This has been fixed.

- In previous versions, when user executes �check code� to unhide a �command


button� a label was visible on the screen. This has been fixed.

- In previous versions, entering '+' or '-' in the middle of a number field was
accepted. This has been corrected.

- In previous versions, when a user clicked on the double arrow (>>) for last
record, data was not refreshed in the Related view. Related records were not
displayed correctly. This has been fixed.

- In previous versions, a Relate button was still visible after a record was marked
as deleted. This has been fixed.

- In previous versions, as soon as the view is opened the relate buttons are not
enabled or disabled correctly. The conditional relate is set up through a check box
value. This has been fixed.

- In previous versions, when a user does a search on all the records including the
records that were marked as deleted are included. This has been changed to show
undeleted records only.

- In previous versions when user navigates to a Relate View menu item is displayed
next to Help menu. This has been changed to show View menu item next to Edit.

- In previous versions in cases where check code is written to unhide a variable


through the last visible control on the form. The system will not move to the
unhidden control. This has been changed to stop in the control in case it is
unhidden.

- In previous versions, if the code tables have empty values they were displayed in
the list. In the current version if do not sort is not set then empty values are
not displayed in the list.

- In previous versions recently used file list, is not updated until you close
Enter. This has been changed to update whenever user changes the MDB and file list
has been increased to four.

- In previous versions of Enter in some situations just using a backspace key. The
system was not updating the changes. This has been fixed.

Epi Chart
---------

- Epi Chart has been changed to not be used as a stand-alone application.

Epi Graph
---------

- In previous versions, it was hard to see the data in the Graph display table.
This has been corrected so that the data is shown in table with the proper font
size.

- In previous versions, Epi Graph plotted subsets (legends) with a maximum number
of 14. With this 3.4 version, Epi Graph can display the number of subsets that are
from the SQL query of crosstab. Epi Graph now uses the latest GigaSoft Graph
Control software, Version 5. There are additional translations and many display
characteristics have been improved.

- The capability of printing all graph pages from the Epi Graph menu has been
added. File > Print All will send all graph pages to the user's default printer.

- In previous versions, editing or changing style to the Pareto right Y-Axis label
and it being changed to the left Y-Axis label has been fixed.

- In previous versions, the Polar graph would not assign the point value to the
tick if the points were less than eight. This problem has been fixed.
- In previous versions, Analysis could not run multiple instances of Epi Graph.
This problem has been fixed.

- In previous versions, the Polar and Pie graphs would not display the main
variables title. This problem has been fixed.

- In previous versions, when passing parameters from a command line, title text is
ahead of stratavar, main title and subtitle would not display. This problem has
been fixed.

- In previous versions, Scatter XY, Scatter 3D, or Step with stratavar would
sometimes get runtime errors and shut the program down. This problem has been
fixed.

- In previous versions, SAVE TEMPLATE did not work correctly. When using a template
not from Analysis and a graph has been customized with colors or font settings, the
graph will be saved as �LastCht.CHT� in the installation directory when closing the
graph.

Epi Map
-------

- In previous versions, Epi Map would cut off part of the image when printing and
would not print in portrait mode without stretching, regardless of the printer
setting. Now, use of the print button on the toolbar will use the current
orientation of the default printer, while the File>Print menu item will allow
selection of a printer and output orientation.

- In previous versions, if the map extent changed, the title did not move to a new
position. Now the title is always at the top or at the bottom.

- In previous versions, where multiple renderings had been overlaid while


deselecting and reselecting an overlay would cause a runtime error. This problem
has been fixed.

- In previous versions, an invalid value for size or width on a Single tab of the
Layer Properties form caused a run-time error. This has been fixed.

- The Map Type menu item has been removed. The same functionality can be accessed
through the Map Manager's Properties button. The Data menu item has been removed.
The same functionality can be accessed through the Map Manager Add Data button.

- In previous versions, moving a graphic (circle, rectangle, etc.) sometimes caused


an error. This has been fixed.

- In previous versions, invalid values for font and character index could cause
runtime errors on the Single Values tab of the Layer Properties form. This problem
has been fixed.

- In previous versions, on the "Records for Features" form when a column was used
for sorting, the form would not close. This has been fixed.

- In previous versions, when a title was specified in Analysis, Epi Map would
display duplicate titles. This has been fixed.

- Epi Map now has a separate area for the user to enter the map title, and the
title is displayed either above or below the map in its own area.
- In previous versions, all of the translation language table strings did not
display or they were not being sent to the translation routine. This has been
fixed.

- Beginning with version 3.2, north arrow, scale bar and tick marks were not
displayed when selected. This has been fixed.

Epi Report
----------

- In previous versions, several messages were not being translated. This has been
fixed.

- In previous versions, the last cell of a table shell could not be formatted
unless there was a value in it. This has been fixed.

- The feature formerly named "Template Build" is now named "Publish Output."

- The '/o' parameter of the command line can now specify either a filename or a
directory.

- In previous versions, carriage returns in multi-line fields were removed when


reports were printed. Now carriage returns in the field will be reproduced in the
report.

- In previous versions, if the user exited a template by clicking on the control


box and then responded "Yes" to the "Save Changes" prompt, an error message
resulted. This has been fixed.

- In previous versions, when closing a template using the control box, an error
message "Error while ruler position is changed" displays. This no longer occurs.

- In previous versions, the format name "scientific" was not capitalized. This has
been corrected.

- In previous versions, the word "column" in the drop-down menu Table Shell was not
spelled out. This has been corrected.

Language Setup
--------------

- In previous versions, labels longer than 140 characters were not being
translated. This has been fixed for the following applications: Epi Lock, Epi Map,
Data Compare and Epi Report.

- The 'T-Setup' has a Create button that allows a user to start up a new working
environment for a language.mdb.

Make View
---------

- In this version, the Data Dictionary has been enhanced to allow a user to view
and define variables for any specific project. Users can now sort and display page
numbers in a View and display the defined variables also.

- In previous versions, while importing a REC file with a two-digit year, the
system always defaulted to 1900 as the century. This has been fixed to allow a user
to make a selection.

- In previous versions, if a user tried to add a field to a table that was over the
limit, it was not added to the REC table. This has been fixed.

- In previous versions, Page is not refreshed until you change the page when a REC
file and a .chk file are imported. This has been fixed.

- In previous versions, if a user does not enter anything for the group name when
adding a group, the system was behaving like a cancel button. This has been fixed
to display a message.

- In previous versions, if a user entered an invalid field type, the system would
give a message to correct the field type. User was not able to cancel until field
type value was corrected. This has been fixed.

- In previous versions, when a user is generating CheckCode with the IF command in


the Before event, the generated code displayed a new line character in the
generated code. This has been fixed.

- In previous versions, if you opened a MDB in �Select a View� form and click on
change project and cancel, it would close the whole operation. This has been fixed
to go to the previous dialog.

- In previous versions, when there are relate buttons on a Child View page, the
HOME and BACK buttons display inappropriately throughout. This has been fixed.

- In previous versions, if users create command buttons with one-character labels


and try to resize them, it can not return to the original size. The minimum default
size has been changed in this current version.

- In previous versions, when all the pages in the page names box are deleted, the
Add, Insert and Delete buttons were enabled when clicked. This has been fixed to
disable buttons.

- In previous versions, if there is an existing code table when importing a .chk


file in a selected MDB, it causes an error. This has been fixed.

- In previous versions, reading an Epi 6 table that included a field named


�UniqueKey� and writing that table in Epi6 produced an Epi 6 table that could not
be read correctly. This has been fixed.

- In previous versions, if a user tried to change legal value type to another type
in the combo, it would not save it. In the current version it displays an
appropriate message.

- In this version users have the ability to use multiple variables from an existing
table for codes.

- In previous versions, of Make View/Enter the system was displaying only one
recently used file in the file menu. This has been changed to display four recently
used files.

- In previous versions, the system would check for the existence of a file with the
Execute command. In the current version that has been fixed. When a parameter is
added the whole string will be enclosed within double quotes.

- In previous versions, when a user created a mirror type variable, the 'variable-
to-mirror' list included CommandButton and Grids. This is fixed so that a list will
not have CommandButtons and Grids.

- In previous versions, if a user typed a very lengthy field name when creating the
datatable, an error was displayed. This was fixed by limiting the length of the
textbox to 64.

- In this version, all the strings and interfaces are translated.

- In this version, a user has the ability to see all the View variables and its
information.

- In previous versions, the captions were not consistent while creating and editing
the labels. This has been fixed to have a group name all the time.

- In previous versions, Make View displayed �Tablename� in the form caption. This
has been changed to display �Projectname� and �Tablename�.

- In previous versions, there was a �How To� sub menu item in the Help menu. This
has been changed.

- Field definition dialog revisions for date variable types are tracked. This
allows changing how to display and enter date patterns.

- In this version, the �Emit� Command name has been changed to �New Record�.

- In this version, the system has the ability to copy all the dependencies, such as
Relates and Grids when the view is copied.

- In previous version, if user adds the resize handles to the command button or a
Relate and activates some other application from taskbar, when returning to Make
View button is hidden.
In the current version this is fixed.

Make View/Enter
---------------

- In previous versions, there was no limit on the length of pattern for number data
types. This has been changed.

- In previous versions of Make View, a user was able to choose a file that did not
have hyphens in the values for comment legal. In the current version strict
checking is enforced.

- In previous versions, if double quotes were not added appropriately when setting
up a conditional statement, Enter would display a gray box. This has been fixed.

- In previous versions of Enter, the New button was displayed when it should not
have been available. This has been fixed.

- In this version there is a new command called EMIT. In Make View, a user can
generate CheckCode for the EMIT command. In Enter when the system encounters this
command, it will save the record and go to a new record.
- In this version, from a full screen or standard screen, settings are always
saved.

- In previous versions, a user could only use variables that were on the current
page. This has been changed.

- In previous versions, Make View was not disabled when user navigated from Make
View to Enter through the Enter Data feature. This has been fixed.

- In previous versions, while creating CheckCode with the same page name and field
variable name, CheckCode would not save correctly. If the CheckCode is written for
a field name, the field should be updated and not the page. This has been fixed.

- In previous versions, using GOTO would lock all controls between the GOTO and its
target. This has been fixed.

- In current version of Make View the �IF� dialog closes when a user clicks on the
�X� button.

- In previous version, when a comma was used with a List of items in write Dialog
command line, the phrase would be cut off. This problem has been fixed.

- Added new command �SETIMPORTYEAR� for Epi 6 import data. The settings for Epi 6
year are YEAR and SPLITYEAR. Edits EpiInfo.mnu file.

- In previous versions, the default database version was Access 97. It has been
changed to Access 2000.

- In this version, a date picker with �DATEFORMAT� for Dialog command has been
added. It serves the date type variable that will be used for Make View or Analysis
data processes.

- In this version, when the Menu module is translated the buttons are saved.

- In previous versions, the Move Button was not translating. This has been fixed.

NutStat
-------

- In previous versions, NutStat only had WHO flags which told a user when the input
data is normal or possibly wrong. This feature reminds the user to double check
their data. In version 3.4 we add flags for CDC reference. The algorithms are new
which only tells if the data is bad; it also tells if the data is normal, too low
or too high. We show those four flags separately:

� Height-for-Age
� Weight-for-Age
� Weight-for-Height
� BMI-for-age

If it is normal, flag=0, background color is yellow. If it is too low, flag=1 and


background color is Red. If it is too High, flag=2 and background color is Red.

Other
-----

- The Birth weight value in record 12 of sample.mdb � Oswego in order to match the
text book has been updated.

-----------------------------------------------------------------------------------
---------

Read Me File (Epi Info Version 3.3.2, February 9, 2005)

Analysis
---------
Merging grid views with a field whose name contained an S no longer produces an
error message.

Two views that relate and have soundex fields of the same name may have an �S�.

Recode expressions of the form x=z can be generated.

The type of a defined variable can be changed by assignment so long as its value
is missing.

MEANS * will produce descriptive statistics (and ANOVA if second variable is


supplied), for all numeric variables.

The denominator feature of the MAP command will work with the COUNT aggregate.

EpiMap
------
Using the Add Points feature of "Vary symbol size for coincident points" and
saving as a shapefile, will no longer result in an error box.

An invalid map template will no longer cause the program to "hang."

All case-based templates will now display correctly.

Installation
------------
Uninstalling Epi Info Version 3.3.2 will not remove EpiInfo.INI file from the
installation directory.

Make View/Enter
--------------
When creating a relationship with a wide table View, the child View may be
accessed from Make View or Enter.

Dates with European formats in a grid will be displayed correctly.

Read Me File (Epi Info Version 3.3, October 5, 2004)


Installation/General
--------------------
In previous versions, Administrator rights were required to run the Report
Generator, Compact and VisData. Now, once someone with Administrator rights
installs Epi Info and shares the installation directory, a profile with User rights
can run all the Epi Info applications.

In previous versions, the most recently added ODBC driver was not available in
the Add/Edit DSN form. This has been fixed.

Check code and analysis programs can now use DBCS (mostly Far Eastern) character
sets for variable names, program names, file names, string constants, etc.

Beginning with this release, Epi Info requires Windows 98 and above to run.

Utilization of form caption icons has been made consistent.

Make View
--------
In previous versions, non-Western characters were not displaying properly on
control captions in a view. This has been fixed.

According to the help topic "Handling Date Fields", paragraph 10, date constants
in Check code or analysis programs must be in US format. In previous versions, this
was not true for Check code. Now it is.

In previous versions, date literals in ASSIGN and IF commands were interpreted


according to the machine�s date setting in Make View, but treated as US dates in
Analysis. Now both programs require US dates.

In previous versions, the Create Data Table menu item did not create the data
table correctly. This has been fixed.

It is now possible to set the default font for the prompts in the View. This
applies only to any new questions added; it will not change existing prompts.
Please see the help topic "Setting a Default Font."

A new property has been added for image fields, Retain image size, which displays
images at their original dimensions rather than stretching them to fit the
designated space.

In previous versions, the user's selection of Access 97 or Access 2000 as the


format for newly created databases was not honored. Now it is.

It is now possible to use DBCS (mostly Far Eastern) character sets for variable
names, prompts, field data, file names, string constants, etc. Note the font chosen
must support the character set of the language.

In previous versions, dates and numbers could not be added. Now they can. Please
see the help topic "Arithmetic (+ - * / ^ MOD)".

A new menu item has been added to the Tools menu, Convert Child to Parent. It is
active for child views and allows the view to access without going through the
parent. The related button in the parent will still exist, but when the user clicks
on it, a message will be displayed that the association between child and parent
has been lost.

In previous versions, when the user defined an option box with text on the left,
the dimensions and location of the option frame were stored incorrectly. This has
been fixed.

In previous versions, if a view was open and the user selected File Open but then
cancelled, the text "Right Click to Create a Field" appeared on the open view. Now
the text does not appear.

In previous versions, when an existing table was selected to be used as a code


table but the field dialog was not then closed, error blocks could occur. This has
been fixed.

In previous versions, the field dialog for fields within a grid displayed the
Codes button enabled even though it was not functional. Now the button is disabled.

In previous versions, if the user created some fields in a view and did not save
it, and then attempted to an import a view, the previously created fields were not
cleared and appeared in the imported view. Now the current view is saved before
performing the import.

In previous versions, the user could edit the field name when the legal value or
code dialog was open, but that would result in an error block. Now the user cannot
edit the field name when the legal value or code dialog is open.

In previous versions, the user was not able to save a field in a grid if another
field in the grid had the same prompt. Now two fields in a grid can have the same
prompt so long as they have different names.

In previous versions, if the user tried use an existing code or legal table that
was a link to different database file, the user received an error block. This has
been fixed.

In previous versions, importing Epi 6 files with short date (month-day) fields
would fail. This has been fixed.

In previous versions, importing Epi 6 files with 8-character European dates would
be imported with either the 20th or 21st century. Now only the 20th century will
be used.

In previous versions, if there was little difference in height between two


fields. Tab order was not calculated correctly. This has been fixed.

In previous versions, the Soundex property was enabled for use in grid fields,
even though it was not implemented. In the current version, the Soundex property is
disabled for grid fields.

In previous versions, if the user created a Relate to a new table with the same
name as an existing table, sometimes a run-time error would occur. This has been
fixed.

In previous versions, when Repeat Last was set for a numeric field and the field
had data, the format value was not cleared if the data type was changed to Text.
This has been fixed.

In previous versions, under certain circumstances Insert Page would fail,


producing an error block and resulting in duplicate page names. This has been
fixed.

In previous versions, after deleting the only page of a one-page view, the page
name was not set properly. This has been fixed.
In previous versions, if the Format Settings menu item was selected and then
cancelled after one of the options had been changed, the next time the Format
Settings menu item was selected it would display the previously selected options.
Now the current settings are showing whenever the Format Settings menu item is
selected.

In previous versions, performing an Alt-Click on the prompt of a legal value


would move the cursor to the top left corner of the view. Now it no longer moves
inappropriately.

In previous versions, it was possible to type in the Check code editor without
picking the variable to which Check code applies. In such cases, the Check code
would not be saved even if a variable was selected later. Now the user is not
permitted to type in the editor until a variable has been picked.

In previous versions, when the user changed a numeric field that had range
validation into a text field, a runtime error occurred. This has been fixed.

In previous versions, when the user changed the variable type to legal values,
the view was not updated and the change was lost. This has been fixed.

In previous versions, if the user opened and cancelled the font dialog in the
field creation form and then opened and cancelled the default font dialog, a run-
time error occurred. This has been fixed.

In previous versions, if the user chose the Import Epi 6 menu item but then
cancelled, an error block was displayed. This has been fixed.

In previous versions, if the Delete Data Table menu item was chosen but then
cancelled, the Create Data Table menu item was nevertheless enabled. This has been
fixed.

In previous versions, when the user moved an option button field, spurious option
buttons were created. This has been fixed.

In previous versions, the user could type Check code into the program editor
without first picking a field to which the Check code applied. This Check code
would not be saved. Now, if the user attempts to do so, a message is displayed that
that the field should be picked first.

In the previous versions, if the user switched pages after adding a new page to a
view but before adding controls, the empty page was deleted without warning. Now a
message is displayed under these circumstances.

In previous versions, when the creation of a conditional relate was cancelled


using the X button, the user was no longer permitted to create a relate button with
the same name. This has been fixed.

In the previous versions the title bar for the Field Definition box was empty
after canceling out of a grid. This has been fixed.

In previous versions, the message displayed when the user attempts to define a
variable that already exists did not get translated. This has been fixed.

In previous versions, when the user selected Change Project, the file dialog was
displayed with a read-only checkbox. Now the checkbox is not displayed.

In previous versions, the MakeView From Data Table menu item was enabled even
when no view was open, even though an open view was necessary for it to execute.
Now this menu item is disabled until a view is opened.

Extraneous information has been removed from the About box.

In previous versions, the Delete Data Table warning message used the critical
error icon. Now it uses the warning icon.

Enter
-----
In previous versions, non-Western characters were not displaying properly. This
has been fixed.

In previous versions, when a FIND was based on a date variable, records were not
found properly on machines using non-US date formats. This has been fixed.

In previous versions, the before and after Check code for the page and record
events was not executed when the user navigated to a record using the FIND dialog.
In the current version the Check code will be executed when the user navigates
using FIND.

In previous versions, when the user did a conditional relate based on a comment
legal field, the relate button was not enabled even though the condition was met.
This has been fixed.

In a multi-user environment when the record being edited has been changed by
another user, a message with Yes and No buttons is displayed saying that data has
been changed by another user. In previous versions, the buttons were not behaving
appropriately. This has been fixed.

In previous versions of Enter, calling a DLL would cause any subsequent function
calls in the same event to fail. This has been fixed.

In previous versions, the result of a yes-no-cancel dialog was of text type


rather than Boolean (yes-no), with the result that it could not be compared with
values. This has been fixed.

In previous versions, date fields in grids were displaying wrong century for some
date values. This has been fixed.

In previous versions, errors in the expression portion of an IF statement in


Check code caused both the true and false blocks to be executed. Now, neither will
be executed.

In previous versions, when Repeat Last was set on a field in a child view, the
new field value came from the last record in the table, regardless of the parent
record to which it was related. Now the new field value comes from the last record
for the same parent.

In previous versions, when the user created a relate field with the property
Return After One Record set, each time the child view was entered a new record
would be created. Now, the same child record will be used each time the user enters
the child view.

In previous versions, when records were marked as deleted, related grid table
records remained undeleted. Now related grid records are marked as deleted.

In previous versions, when the user deleted a previously-assigned text field


size, the underlying view was not updated. This has been fixed.
In previous versions, if there were more than 3 option buttons on the screen,
they could not be reached by tabbing. This has been fixed.

In previous versions, when Enter was used to compress the database, it sometimes
would be lost. This has been fixed.

In previous versions, an invalid size error occurred if no size was entered for a
text field and the type of control was changed. In the current version this has
been fixed.

In previous versions, if the code value of a code table began with a space, only
the first field based on the lookup would be populated. In the current version, all
lookup fields populate correctly.

In previous versions, mirror fields could hold only limited text. In the current
version, multiline fields will be mirrored into multiline fields.

In previous versions, when the user changed screen resolution, the size of option
frames would change. In the current version, the frame occupies the same proportion
of the screen in all resolutions.

In previous versions, if Make View had been exited by closing a child view
without using OK, Enter would display an error block when the Relate button was
clicked. This has been fixed.

In previous versions, if a permanent variable was set equal to a date field in


Check code, the permanent variable was not stored correctly. This has been fixed.

In previous versions, closing the select view form with the X in the title bar
gives the message "The view is related to a parent view. Please open the
parent ..." Now clicking the X button acts like the cancel button.

When the user opens a view and changes the page without entering data, a dialog
is displayed asking the user whether the record should be saved. In previous
versions, if the user clicked on the X button it, an error block would be
displayed. This has been fixed.

In previous versions, when a form of the dialog command using a database was
executed, an error block was displayed. This has been fixed

In previous versions, if the user performed a Find and then went to a related
view, the search criteria for the Find would be lost. Now the search criteria will
be retained until the user does a Find in the related file.

In previous versions, when the user deleted a record, any Relate buttons in the
view remained active. Now they are made inactive.

In previous versions, if there was a conditional relate which depended on the


value of the last field on a page, when the user pressed TAB or ENTER control would
flow to the next page or record without giving the user the opportunity to work
with child records. Now, if changing the last value on a page causes a conditional
relate to become active, control flows to the relate button.

In previous versions, Enter had a menu item Compress Database. This item is now
called Compact Database and its behavior is the same as the Epi Info utility
Compact.
In previous versions, the Select Table dialog was not being translated. This has
been fixed.

In previous versions, when the user selected Change Project, the file dialog was
displayed with a read-only checkbox. Now the checkbox is not displayed.

Extraneous information has been removed from the About box.

Analysis
--------
In previous versions, dates used in RECODE and GRAPH (Histogram) command
generation screens had to use local date format based on Regional Settings, while
the command used US date format for syntax checking. Now dates in command
generation screens must be in US date format.

In previous versions, the user could run other commands while LIST UPDATE was in
progress. This is no longer true.

In previous versions, when the report generator was run from Analysis, it did not
see permanent variables defined or assigned a new value during the current analysis
session. This has been fixed.

In previous versions, numeric variables could not be used as the outcome variable
in logistic regression. Now this is possible. Records with non-zero values will be
treated as true, with zero values will be treated as false, and with missing values
will be excluded from the analysis.

New Analysis commands have been added to delete records, tables and fields and to
undelete logically deleted records. Please see the help topics "Delete File/Table",
"Delete Records" and "Undelete Records" for details.

A new aggregate function, CASE-BASED, has been added to the MAP command to invoke
the case-based mapping functionality of EpiMap. For details, please see the help
topic "Map".

In previous versions, the Soundex code fields associated with text fields with
the Soundex property were not accessible from Analysis. Now they are. If the
associated text field is changed using LIST UPDATE, the Soundex field will be
updated when the window is closed. The Soundex fields of records added using MERGE
can be set by running LIST UPDATE.

The Analysis REPORT command will now display the report in preview mode if the
keyword DISPLAY is used in place of a printer name.

In previous versions, when using Epi 6 Direct Read, Epi 6 yes-no variables would
be read as string variables with values "1", "0" and " ". They are now read as yes-
no variables with values (+), (-), and (.). This means that if they are re-exported
to Epi 6, they will be the same as the original file.

In previous versions, if the portion of a command before a line continuation


character was a valid command, clicking on the first part of the command then on
Run This Command would result in only the first part of the command being executed.
This has been fixed.

In previous versions, when a file which was to be included in Analysis output by


means of the TYPEOUT command lacked a <BODY> tag, the command failed without
warning. Now, a message is given.

In previous versions, if missing was set on and a variable only had missing
values (or only had missing values for one stratum when a strata variable was
used); other frequencies, tables and means being run at the same time would fail.
Now they will not.

In previous versions, multiline variables failed in frequencies, tables and


means. Now they can be included, but only the first 255 characters will be used.

In previous versions, the Analysis XML output for the report generator did not
reflect the setting of the Show Full Prompts option. Now it does.

In previous versions, the Analysis XML output for the report generator did not
include line numbers as did the HTML output. Now it does.

In previous versions, ROUTEOUT caused an error unless a full path was given. Now,
the command creates the output file in the directory of the current project if no
path is specified or the directory does not exist.

In previous versions, attempts to use a DLL method in the expression of an IF


statement gave the error message "Operators must be of compatible types". Now this
no longer occurs. Note that in Analysis DLL methods cannot use expressions
involving field variables as arguments.

In previous versions, outtables did not function correctly in complex sample


routines. This has been fixed.

In the past, LIST UPDATE showed "Expr###" as the label for columns containing
defined variables. Now it will display the variable name. Note that defined
variables cannot be updated using LIST UPDATE.

In previous versions, when the FREQ command was used with multiple variables and
the names of those variables were substrings of each other (e.g., FREQ Age Wage), a
spurious line with a missing value and 0 counts appeared in the output. This has
been fixed.

In version 3.2 of KMSURVIVAL, specifying a group variable with only one value
resulted in unrecoverable error messages. Now, as in earlier versions, a survival
graph for all cases is produced.

When reading a non-Epi Info data table, a field containing only null, 0, and
either +1 or -1 should be interpreted as a yes/no field. In earlier versions, this
did not happen if the field contained a null. This has been fixed.

In previous versions, MEANS * would sometimes fail. This failure no longer


occurs.

In previous versions, sometimes logistic regression would not converge to a


solution where other products would do so because the initial estimate fell outside
the convergence space of the algorithm. Now, the initial estimate is chosen so as
to converge to a result where one exists.

In previous versions, the Analysis MAP command would not run in silent mode if a
template was specified. This has been fixed.

In previous versions, the GRAPH command generator screen showed the "Show single
cases" button under the wrong circumstances. This has been fixed.

In previous versions, it was not possible to read Access and ODBC tables with
spaces in their names. Now it is.
Due to changes in the underlying database services, some calculations which had
previously produced numeric outputs can now produce date outputs, with the
consequence that type errors are generated. Now, these calculations have been
changed to eliminate the errors while maintaining the previous type behavior.

Due to a change in the underlying system functions, strata variables may not be
printed. Furthermore, decimal strata variables may not be printed with appropriate
precision. This has been fixed.

In previous versions, decimal numbers in Epi 6 files were misinterpreted on


machines with European number format. This has been fixed.

In previous versions, after creating a map, the GRAPH command would sometimes
fail. This has been fixed.

In previous versions, when no output file was specified and a file already
existed with the name built from the information on the Storing Output screen, the
output would be appended to the existing file. Now a new output file will be
created.

In previous versions, the command generation screen for MAP sometimes offered *
as a geographic variables even though * is not a permitted value. It no longer does
so.

In previous versions, the Match command would accept * for the row or column
variable when this is not permissible, resulting in an error block. Now these
situations result in a custom message and return the user to the Gen screen or
program, depending on where the problem arose.

The SQL generated for null tests has been changed to reduce the complexity of the
expression.

In previous versions, the XML report generator output for the complex sample
means command contained a standard error which was 100 times that reported in the
HTML output. This has been corrected.

In previous versions, box-whisker graphs could not be produced for a variable


named VARNAME or COUNT. This has been fixed.

In previous versions, when running complex sample means, a defined but unassigned
outcome variable caused unrecoverable errors. This no longer happens.

In previous versions, when using the command generator to generate the GRAPH,
FREQ, TABLES, MEANS and advanced statistics commands, it was possible to cause
variables to appear more than once in the available variable list. This has been
fixed.

In previous versions, MEANS * and TABLES * <varname> did not work if there were
any defined variables. This has been fixed.

In previous versions, if the Build Key dialog for RELATE and MERGE was closed
using the X in the upper right corner, the Build Key button thereafter produced
help. This has been fixed.

The handling of errors during the read/import of Epi 6 files has been improved.

In previous versions, attempts to use the MERGE command when the READ table was
not Epi Info or MS Access type caused a series of error messages. Now, attempts to
merge data into unsupported file type�s results in an explicit error message to
that effect.

In version 3.2.2, the SUMMARIZE command did not work with the COUNT() aggregate.
This has been fixed.

In previous versions, it was not possible to omit the path when reading an Epi 6
REC file in the current project directory. This has been corrected

In previous versions, errors occurred with some file types when writing a defined
variable set equal to UniqueKey. This has been corrected.

In previous versions, Excel files with a name part longer than 8 characters could
not be read. Now they can be.

In previous versions, after reading a non-Epi Info table, such as an Excel


worksheet, the command generator for RELATE and MERGE displayed other data sources
of the same type instead of the current project tables. This has been fixed.

In previous versions, reading a table not part of an Epi Info View could cause an
overflow error. This has been corrected.

In previous versions, in Complex Sample routines, if the PSU variable was a


defined variable set to missing, an unrecoverable error would occur. Now this
produces a single error message.

In previous versions, specification of a defined but unassigned variable for SORT


would not produce an error message, and subsequent LIST and WRITE commands would
fail. Now, SORT will produce an error message and subsequent commands will not
fail.

In previous versions, after generating a GRAPH command for a hi-low graph, the
command generation screen for graph was not displayed properly. This has been
fixed.

In previous versions, running MEANS * with a table that contained no numeric


variables would produce an error block. Now the same circumstances will produce a
customized error message.

In previous versions, reading an Epi 6 table that included a field named


uniquekey and writing that table in Epi6 produced an Epi 6 table that could not be
read correctly. This has been fixed.

In previous versions, reading an Excel 3.0 or 4.x worksheet and then writing it
in the same directory in the same format sometimes failed with an error message
that the database was read only. Now this has been fixed.

In previous releases, it was possible to specify a defined but unassigned


variable as the PSU variable for Complex Samples without receiving a specific error
message to that effect. Now a message to that effect is displayed.

In previous versions, it was possible to specify text variables in the MATCH


command without receiving a specific error message to that effect. Now a message to
that effect is displayed.

In previous versions, when the user clicked on the New button in the program
editor, all the commands in the editor were cleared. Now a message is displayed to
verify whether the user wants the commands cleared.
In previous versions, when generating a READ command using delimited files on a
machine where Excel was associated with those file types, a hidden preview window
would be opened, causing the read to fail because the file was in use. Now, the
file preview window for these file types will not use Excel and will not be hidden.

In previous versions, some error messages relating to the DIALOG command did not
match the vocabulary of the command generation screen. This has been changed.

In previous versions, the LIST UPDATE command did not change the cursor to
indicate busy status. This has been changed.

In previous versions, a change was made to add single quotes around table names
in the READ command generator when the data source was ODBC. This has now been
extended to RELATE and MERGE.

In previous versions, there were situations where output was not being
translated. This has been fixed

In previous versions, Epi 6 direct read of file whose extension is not REC would
create file of the same name with a .rec extension which is not an Epi 6 .rec file.

In previous versions, the print button on the output window remained depressed
and disabled for 30 seconds after clicking to enable the printing to take place.
Now the delay is only 20 seconds, during which the image and caption change to
indicate more clearly what is going on.

In previous versions, when generating a READ command, if there were no Epi Info
views in a project, an empty list would be displayed. Now the list of all tables
will be shown.

EpiGraph
--------
In previous versions, the moving average was not displayed properly on Moving
Average type graphs when there were missing values in the data. This has been
fixed.

In previous versions, graphs were not plotted for missing values of the strata
variable even when Include Missing was selected. Now they are.

In previous versions, there was a Display Data menu item. Now this item has been
removed. A more complete version of this feature can be found in the Customization
dialog.

In previous versions, date variables were displayed in numeric format in scatter


XY and step graphs. This has been fixed.

In previous versions, when a pyramid graph had a cross-tabulation variable with


only a single value, a message was displayed that a cross-tabulation variable was
required, but it would proceed to generate an appropriate graph. Now the message
has been removed.

In previous versions, when a graph template was created with fewer x-axis points
than the number present in the data being graphed, the additional points would be
displayed in an area which could be reached by use of a horizontal scrollbar. Now
the scrollbar has been removed and all points are displayed in the visible portion
of the graph.

In previous versions, the Y Axis would sometimes become crowded with labels and
tick marks. This problem has been fixed, except for Horizontal Bar and Pyramid type
graphs.

In previous versions, the Hi Low graph would in some cases result in a series of
errors. This has been corrected.

In previous versions, graph background colors were not stored in the graph
template. This has been fixed.

In previous versions, when a graph template was created from a graph with a
strata variable, strata information was being saved in the subtitle of the graph
template. Now this is not done.

In previous versions, when a graph template was created from a graph with a
strata variable, the save template dialog was displayed once for each page. Now it
will display only once.

In previous versions, Y Axis labels on Pyramid graphs were partially blocked out.
This problem has been fixed.

In previous versions, if a template was used that had been created with a smaller
number of points on the horizontal axis than the current data source; the
additional points could only be seen by use of a horizontal scrollbar that did not
appear in the Analysis output window. Now all points in the current data source are
displayed without a scrollbar.

In previous versions, the Set Y Axis Style menu item was available for Pie,
Polar, Scatter 3D and Pyramid graph types, even though the setting is not
applicable to them. Now this menu item is disabled for these graph types. Also, the
Set Y Axis Style will not be accessible when the Y Axis labels are dates.

EpiMap
------
In previous versions, a dot density rendering could not be displayed over a case-
based rendering, nor could such a map be created through a template. This has been
fixed.

In previous versions, when data was added to a layer and it was displayed as
something other than a choropleth, the saved template would still have a choropleth
setting. This has been fixed.

In previous versions, when multiple layers used the same shape file the map would
not be displayed properly. Now the order of the layers in the map manager
determines the display order, while the currently selected layer determines which
legend is drawn.

In previous versions, if Advanced Labels were added to a map and set to a large
size and the map saved as a template, the label size would not be restored
properly. This has been fixed.

In previous versions, when a Dot Density rendering was displayed over a Unique
Values rendering, the Unique Values display and/or its legend were not saved in a
template file. This has been fixed.

In previous versions, when multiple shape files were used on different layers and
their data was represented in multiple ways, a variety of errors occurred. This no
longer occurs, although there still may be particular combinations which fail.

In previous versions, when Add Points was cancelled after selecting a data source
for the point data, the data source was not removed from the map. This has been
fixed.

In previous versions, if a map created from Analysis specified both a title and a
template containing a title, EpiMap would use the template's title. Now, any title
from Analysis will override the template's title.

In previous versions, the Layer Properties dialog tabs were not translated. This
has been fixed.

In previous versions, after creating a map from Analysis using a template and
resaving to a new template with changed individual colors, the loaded choropleth
map turned black. This has been fixed.

In previous versions, when producing a map from Analysis, if the geographic


fields were of different types, an error block would be produced. Now a customized
data type mismatch error message will be displayed.

In previous versions, if two Choropleth renderings were done on two shapes files
and the ramp colors or number of choropleth classes was changed for one of them,
the changes would not be saved to a template. This has been fixed.

In previous versions, if a dataset failed to join with a shape file when


generating a Case-Based map, the Case-Based button would be disabled even though no
map had been displayed. Now, the Case-Based button remains enabled if generating a
Case-Based map fails.

In previous versions, if the shapefile had no text field or the data table had
either no text field or no numeric field, a message was displayed and thereafter it
was impossible to select another table. This has been fixed.

In previous versions, if the user created a Unique Values rendering when a value
for a Unique Layer was missing, a run-time error would occur. This has been fixed.

In previous versions, if a language other than English was used when creating a
shape file, standard fields such as "name" and "area" was saved with the wrong
names. This has been fixed.

In previous versions, map templates were not saved properly on machines using
non-US number format. This has been fixed.

In previous versions, clicking on other property tabs immediately after applying


a dot density with overlay would cause a runtime error. Now the runtime error will
not occur, but there are still situations where an overlay on top of dot density
will not save properly.

In previous versions, selecting the Background Image menu option when there was
no background image or when loading was cancelled or failed caused a run-time
error. Now this menu item is disabled in those circumstances.

In previous versions, when points, lines or shapes were added to a map, or when
case-based mapping were used, typing an invalid symbol name or size would result in
an unrecoverable error. Now, in these circumstances, valid default symbols and
sizes are used.

In previous versions, the Add Points button would remain enabled after the user
added data to the layer. Now it is disabled.

Epi Report
---------
In previous versions, when creating a new DSN in the Report Generator, help was
sometimes not available. This has been fixed.

In previous versions, if the user printed or previewed the report, the row data
was sometimes getting cut when the table spanned multiple pages. This problem has
been fixed for most of the tables. For the tables that fail, an option is still
available to print using the functionality provided by version 3.2.2. Besides this,
there is a new feature to insert a page break at the desired position on the
template.

In previous versions, when two or more elements overlapped in the template


designer, they became disconnected when the report was generated. This has been
fixed.

In previous versions, the tree did not display the newly added nodes (line
listing and pivot table queries, analysis table and field aggregates) immediately
after the user added them. Now the tree expands and highlights the new nodes in
bold.

In previous versions, there was no way to know whether any new commands were
added to an existing Analysis XML file. Now the designer displays the command
selector dialog when new nodes are found.

In previous versions, fonts not based on the Latin character set were not fully
supported. Now they are.

In previous versions, there was no way the user could terminate the report
generation process. Now a cancel button is provided, which will return the user to
the designer.

In previous versions, after a table pair was selected in the relate tab of the
query builder, there was no way to tell the table to which a field list belonged.
Now each field list is labeled with the table name.

In previous versions, there was no way the user could hide or move the toolbar
buttons. Now they are categorized by functionality and split into different groups
which can be hidden or placed separately. Also, another group has been added for
setting the width or height of the selected element without invoking the property
window.

In previous versions, the only way to add vertical space to the bottom of the
template was through CTRL+J. Now a button to do so has been added in the toolbar.

In previous versions, special characters and symbols were not allowed in query
names. Now they are.

In previous versions, when the print menu item was chosen after generating a
report, the print dialog was hidden. This has been fixed.

In previous versions, when the print toolbar button was chosen after generating a
report, the print dialog was displayed. Now it is not.

In previous versions, an unnecessary message was displayed when editing a line


listing or pivot table query consisting of memo fields. Now it is not.

In previous versions, when adding a table from Analysis, formatting changes such
as border styles and colors were not being retained. Now they are.
In previous versions, line listing output at the grand total level showed the
name of the aggregate plus the word "$Grand." Now only the aggregate name is shown.

In previous versions, clicking the Clear button in the query builder screen for
pivot tables caused an error message. This has been fixed.

In previous versions, if data for line listing and pivot table output contained
valid HTML, it was interpreted and rendered as such in the table cells. Now the
data is treated as plain text.

Menu
----
In previous versions, when a variable was defined but not assigned and then was
used in macro substitution (@@), the program would hang. This has been fixed.

Data Compare
------------
In previous versions, opening an invalid script file would stop the current data
comparison. This problem is fixed.

In previous versions, the field comparison number and percent values in the
comparison report were incorrect. This has been fixed.

In previous versions, the Data Compare statistics report showed the percent
difference only to the nearest percent. Now it will display as many as 4 decimal
places.

Epi Lock
--------
In previous versions, if the user entered a wrong password when decrypting a file
using 40-bit encryption, no message was displayed. Now a message is displayed.

In previous versions, passing an erroneous command line parameter would result in


duplicate error messages. This has been fixed.

In previous versions, passing an erroneous command line parameter would leave a


hidden copy of the program running. This has been fixed.

Tbl2View
--------
In version 3.2, Tbl2View produced views which could not be updated with Check
code. Now, when opening views in Enter or projects in Analysis, the structure of
the views will be updated to the current version.

In previous versions, Epi Info fields were added to the table even if the
operation was cancelled. Now this does not occur.

In previous versions, code tables were not converted correctly. This has been
fixed.

When the user chooses a table name containing a space, the program prompts for
selection of a different name. In previous versions, if the replacement name
matched the name of an existing table, a runtime error occurred. Now a message to
that effect is displayed and the user is prompted to enter a different name.

In previous versions, choosing a Jet reserved word as a field or table name


caused a runtime error. Now the user will be asked to change the name when a
reserved word is discovered.
NutStat
-------
In previous versions, reports could not be generated when the data table had a
space in its name. This has been fixed.

In previous versions, during a batch update, BMI, MUAC and Head Circumference
statistics were not added even when the reference was set to 2000 growth curves.
This has been fixed.

In previous versions, the options screen had a label reading "Weight For Height".
This has been corrected to "Height For Weight".

In previous versions, a runtime error occurred when a report template was run
against a different data table than that in use when it was created. Now a report
template can be used regardless of what table was used when the template was
created.

In previous versions, inappropriate help was displayed when the user pressed the
F1 key on the main screen. This has been fixed.

Help
----
The help section for the HELP command was improved.

ReadMe (Epi Info, Version 3.2.2 April 14, 2004)

General
-------
Newly created MDBs will now be created according to the database version set in
Menu.

The window displayed when executing the Dialog command will now adjust its size
according to the length of text for the prompt.

Analysis
--------
The feature which permits the user to specify a database on the Analysis command
line and have it used as the default now functions correctly.

In prior versions, if the directory path to the current project included any
spaces, maps would be generated but not displayed in the Analysis output.

Analysis/EpiGraph

-----------------
In prior versions, when the GRAPH option TITLETEXT was used, the title string
appeared both as the overall title over the graph image(s) and as the main title of
each graph. Now, if multiple graphs are being created (i.e., a STRATAVAR is
specified), the TITLETEXT string will be displayed only as the overall title. If
the TITLETEXT contains the pipe character ("|"), the string to the left of the pipe
will become the overall title and the string to the right of the pipe will become
the main title of each graph. If only one graph is being created (i.e., there is
no STRATAVAR), the TITLETEXT string will be displayed as the main title of the
graph. If the TITLETEXT contains the pipe character ("|"), the string to the left
of the pipe will become the main title and the string to the right of the pipe will
become the subtitle. These titles will override any specified in a template, if
one is specified.

The legend will now display even if there is no cross-tabulation variable.

In prior versions, null stratification values were not graphed. However, a


limitation remains still for Scatter XY, Hi-Low, Box-Whisker, and Step graphs.

When graphing with a weight variable, error messages were produced if the weight
variable had missing values. Now records with null weight variable values are
skipped.

A new date format applicable to time-only values has been included in those
provided in the GRAPH command generator screen. It should be noted that users are
not restricted to the provided formats, but can enter their own custom format.
This capability does not include Scatter XY, Hi-Low, Box-Whisker, Step and Scatter
3D graphs.

An error message stating that a cross-tabulation variable is required for a Stacked


Histogram graph has been removed.

Graph will now display a Cross-tabulation (CROSSTAB) and/or strata variable


(STRATAVAR) legend when there is only one value.

Graph page title is now centered.

Graph images will now consistently be sent to the output window.

The EpiGraph menu has been slightly changed for improved usability.

Installation
------------
OfficeSetup is now executed from Setup to fix a known Microsoft Office problem with
executing DHTML edit control (used by Epi Report). See
<http://support.microsoft.com/default.aspx?scid=kb;en-us;Q304107>. This had been
removed from Version 3.2 as it was thought to be no longer necessary.

When Epi Info, Version 3.2 was uninstalled, the "Open Link in New Window" option
(when right-clicking on a link) did not work.

When Epi Info, Version 3.2 was uninstalled, the Add/Remove Programs from Control
Panel states that there are no programs installed on the machine. Upon scrolling
down, the programs would appear, but the buttons were all grayed out.

Epi Info now installs MDAC 2.7 Refresh to handle a known issue with Microsoft SQL
Server service pack 3. A detailed description of the issue is available at
<http://support.microsoft.com/?kbid=814572>.

Epi Graph now runs properly the first time the Graph command is executed from
Analysis.

An Epi Report error message is no longer displayed as soon as OK is clicked in the


MDB selection dialog.

On a machine with MDAC 2.7 SP1 uninstalling and reinstalling Epi Info, Version 3.2,
causes all the applications that use ADO (Advanced Statistics in Analysis, Epi Map
and Epi Report) to throw errors. This does not happen with version 3.2.2.
Make View/Enter
--------------
DIALOG commands which assign values to a variable will no longer produce an error
message.

Check code will now run in multiline variables.

An error message will no longer display if clicking on the Program button and then
clicking on Insert Page.

Table-to-View
-------------
In prior versions, if there was a space in the table name, Table-to-View would
automatically replace them with underscores in the view name but not the table
name, causing problems with the table. Now, the user has the opportunity to rename
the data table if it does not have a valid Epi Info name.

In prior versions, if the user selected an empty database, the program proceeded to
the next screen. Now, the user cannot continue if there is no table available.

In prior versions, the View table was created with the Check code field as Text
instead of Memo which limited the amount of Check code which could be entered.

In prior versions, View tables were permitted to be converted to a new View.


Table-to-View will no longer show View tables in the table list.

A field called ID will no longer be created when converting from a table to a View.

ReadMe (Epi Info, Version 3.2, February 4, 2004)

Analysis
--------
Date values in the INI file (permanent variables) are now recognized.

Menu
--------
In prior versions, it was not possible to pass in multiple command line parameters
when using the EXECUTE command.

ReadMe (Epi Info Version 3.2 January 22, 2004)

General
-------
On machines that have a non-US number format setting, numbers can be entered into
dialog boxes produced by the DIALOG command using either the US decimal point (a
period) or the machine's local decimal point setting found in Control
Panel/Regional Settings (normally a comma).
Date values in the INI file are now being stored in local format, so when INI files
are exchanged between machines that use different date formats, the INI file must
be manually modified to express dates in local format.

On machines that have a non-US date format setting, dates must be entered into
dialog boxes produced by the DIALOG command using the machine's local date format
as found in Control Panel/Regional Settings.

Analysis
--------
In prior versions, it was possible to specify a defined but unassigned variable as
the PSU variable for Complex Samples without receiving a specific error message to
that effect.

In prior versions, it was possible to specify text variables in the MATCH command
without receiving a specific error message to the effect.

In prior versions, while using the TYPEOUT command when a file lacked the <BODY>
tag, the command failed without warning. A message is now displayed when a file
lacks the <BODY> tag using the TYPEOUT command.

When using Epi 6 Direct Read in prior versions, Epi 6 yes/no variables were read as
string variables with values "1" and "0". They are now read as yes/no variables
with values (+), (-), and (.). This means that if they are re-exporting to Epi 6,
they will be the same as the original file.

In prior versions, the number of degrees of freedom reported for matched


(conditional) logistic regression was one too high, which resulted in probabilities
higher than that which should have been shown.

In prior versions, when FREQ, TABLES or MEANS was run with a defined variable as
the weight variable, a spurious error message, "Weight must be numeric variable",
appeared.

In prior versions, the logistic regression procedure incorrectly determined that it


was failing to converge and stopped computation with a message to that effect.

Menu
----
An OnBrowserExit command has been added. The OnBrowserExit command is executed when
the user clicks the Close button on the browser window that is generated from Menu.
This command works similar to the StartUp and ShutDown command.

The string IniPath and InstallDir in the Epi Info Registry now includes a
backslash. This change will not change the Epi Info system variables, IniDir and
InstallDir.

Epi Report
----------
The Line Listing Group feature now allows for the spanning of cells of the group
row.

The header �EpiRepGen� that was displayed in the Windows Task Manger dialog box has
been changed to display �Epi Report�.

The prefix and suffix of date values in the SELECT tab of the Query Builder has
been changed from single quotes to the �#� sign.

The Footer row in Line Listing now spans all the cells after new columns are added
to the existing query.

Borders now appear if the fetched value is null for any of the cells in Line
Listing.

The correct value is now fetched for the grand total that is defined at the bottom
of the report.

The Office-CD Fix menu item has been removed from the Epi Report Help drop down
menu. The new installation routine has eliminated the need for this feature.

The performance speed of Epi Report has been improved in several areas including
report generation.

WHAT'S COMING WITH EPI INFO 7


-----------------------------
The next generation of Epi Info is available. Download Epi Info 7 from the CDC
website at
http://wwwn.cdc.gov/epiinfo/7/index.htm

The benefits provided by Epi Info 7 include the following:


- Collect more data with more fields than Epi Info 3.5.4 allows.

- Collect data on available SQL Server Databases -- as well as local MS Access-


compatible files.

- Collect data concurrently in a multi-user environment.

- Create electronic forms by dragging and dropping standard public health questions
and templates.

- Create partial questionnaire templates that can be reused or shared to accelerate


electronic form creation.

- Customize electronic forms to exactly match paper-based forms, including paper


size and layout.

- Assign skip logic, including new geocoding logic, to electronic forms.

- Analyze data without leaving the data entry screen using frequency, means, and
cross-tabulation gadgets.

- Link records together to create exposure relationships.

- Visualize data on new case-based cluster maps and social network analysis graphs.

- Distribute, deploy, and use Epi Info 7 without needing elevated privileges on a
computer.
* Epi Info 7 does not need to be installed. Epi Info 7 can run from a USB drive,
from a CD, or from shared network locations.

* Epi Info 7 requires much less disk space than the current version and can be
distributed in a ZIP file.

While almost all of the functionality of Epi Info 7 MakeView and Enter tools have
been completed, there is still more to come. In the near future, Epi Info 7 will
enable you to:

- Analyze more data than currently possible.

- Analyze data directly from enterprise data sources available on SQL Server
databases.

- Perform all advanced analytical functions that are available with Epi Info 3.5.3
including stakeholder requested enhancements as applicable.

- Perform all mapping functions that are available on the current version of Epi
Info while connected to larger SQL Server datasets.

- Quickly generate reports using drag and drop functionality to transform data into
usable information.

- Request and download specialized analytic functions and dynamically add them to
Epi Info 7.

Please report any issues to the Epi Info Help Desk at EpiInfo@cdc.gov.