New Features & Bug Fixes in betaDataFerrett

Last Updated on October 12, 2011



NEW FEATURES

* New * A user may now include data cells from more than four detailed tables in a single extract request; i.e., there is no longer a limitation of four tables per extract request.

* New * Since the initial release, the "Make a Table" path (including mapping) has been much more thoroughly tested and many problems have been corrected.

* New * The margins of error (MOEs) are now treated as attributes of the estimates. This means they are no longer selectable as indpendent variables. The user can now choose to include or exclude the margins of error in an extract. If they are to be included, they can be output in a separate file or interleaved with the estimates in a single extract file. This new approach to the treatment of margins of error also affects their display and what can be done with the MOEs in the "Make a Table" window of DataFerrett.



BUG FIXES

Fixes as of October 12, 2011

Problems with SORT feature in "Make a Table" window

Previously there were problems that occured in a table (in "Make a Table") when the SORT feature was used in conjunction with the feature allowing the user to show every data column as a percentage of the first data column (the leftmost % column icon). This resulted in the percent data becomming associated with the incorrect state.


View/Modify action now able to delete geographic areas

When a user would attempt to use the View/Modify action in Step 2 to delete one geographic area from a geographic variable added to the data basket in step 1, the area will disappear from the list without actually being deleted. This causes the unwanted geographic area to appear in the data extract or table the user created using this geography variable.


Errors in SAS code corrected

When a user would specify an extract in SAS file format, the generated SAS code would sometimes contain an error in a SAS format statement "the same value is equated with two or more different labels".


Geography Selection Wizard now retains higher level geography

Geography Selection Wizard "if the user selects geographic areas from the geographic "hierarchy" (e.g., state-county-tract) by selecting the higher level geography followed by the lower level geography before hitting the "Finish" button, the selections for the higher selected geography would not be retained. The user can now retain both the higher and lower selected geographies.


Fixes as of May 31, 2011

Tabulating a mean variable across multiple instances is now fixed.


The DataFerrett "Browse/Select Variables & Values" window is no longer unresponsive without notifying the user when an invalid value has been entered in the minimum or maximum range field.

Previously, the DataFerrett "Browse/Select Variables & Values" window froze when a user entered an invalid value in the minimum or maximum range fields for a variable that contains range values. Now, should an invalid value be entered, a warning dialog is displayed indicating a valid numeric value is required.


DataFerrett now provides a warning to users who attempt a Multi-variable Data Step recode with aggregate and geographic variables together.

The warning now states: "Dataferrett does not support multiple variable recoding for geography with any other variable." Previously, this function returned invalid results without warning the user when such a step was attempted, as the Multi-variable Data Step recode using aggregate and geographic variables together is not allowed.


A generated SAS code no longer contains an error in the SAS format statement when a user requests an extract in SAS.

Previously, a user sometimes received the folloiwng error message when attempting to execute the generated code: "The same value is equated with two or more different labels."


In the Geography Codebook window, the higher level geography selection is now retained when a user subsequently selects lower-level geographic areas from the geographic "hierarchy", (e.g., state-county-tract), before clicking on the "Finish button."

Previously, if a user selected a geographic area from the geographic codebook hierarchy, the higher level geography associated with it, i.e. a state in which counties are selected, was not retained if the "Finish" button was not clicked on at each stage of the geographic selection process.


The "Hide","Insert", and "Delete" menu choices in the Ferrett Tabulation window are no longer active if appropriate column or row selections have not been made.

Previously, the "Hide" "Insert" and "Delete" menu items in the Ferrett Tabulation window were erroneously active as user choices without the appropriate column or row selections.


The Geographic Codebook window now properly displays previously selected geographic values in the selection box of the Codebook window when modifying a selected geographic variable in the "Step 2" environment of DataFerrett.


A user can now cancel out of saving a session (.fsf) or tabulation (.ftf) file, continue to work, and then return to the file save option to save the same session or tabulation files.

DataFerrett no longer closes unexpectedly if a user attempts to save a current DataFerrett session or tabulation window, then clicks "Cancel" before completing the "Save", does more work, and then tries to "File --> Save As" again.



New Features - Archive

May 31, 2011