|
.gif) |
What's New in Epi Info 3.4.3!
Epi Info 3.4.3 is a minor release to correct a critical flaw in version 3.4.2.
Here is a list of the changes and enhancements that went into release 3.4.2.
For a comprehensive list of all changes, enhancements and bug fixes, see the
ReadMe.txt file.What's New in Epi Info 3.4.2!
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 has 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 type or value. Now, date functions passed a variable
with no type or value always return a null value (missing) with no error message.
Common
- 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
- In previous versions, the"@@" replacement operator returned a wrong value
of a dot/period (".") when used with a permanent variable that had an null
value. This problem has been fixed.
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, 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.
- 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.
MakeView / Enter
- In the 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 the 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. |
|
