EPI INFO VERSION 3.5.1 READ ME FILE 08/11/2008 TABLE OF CONTENTS ----------------- INTRODUCTION END-USER SYSTEM REQUIREMENTS INSTALLING EPI INFO 3.5.1 CHANGES IN EPI INFO 3.5.1 KNOWN ISSUES IN EPI INFO 3.5.1 INTRODUCTION ------------ Epi Info 3.5.1 is an upgrade release to version 3.5 of Epi Info. The latest version of the Epi Info software was enhanced to include Windows Vista compatibility. 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. END-USER SYSTEM REQUIREMENTS ---------------------------- 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. WINDOWS XP and Vista 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.1 ------------------------- To install Epi Info, administrative or power user rights to the computer are required. - Vista Users only. Before installing Epi Info 3.5.1, remove any prior versions of Epi Info. - 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 - Before installing Epi Info 3.5.1, remove any prior versions of Epi Info. - 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 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
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 *