Release 6.40.9

Improvements

•	Double quotes in values were not correctly handled in the excel wizard (09/26/2011).

Release 6.40.8

Improvements

•	Specific combinations of values in records could result in these records being considered equal in a projection. Such records were not included in reports, table sections and related functions (09/19/2011).

Release 6.40.7

Improvements

•	When, in the internal report, the user edited the cell content in place or in the entry field and then changed the cell content using zoom operations before exiting the entry field, an incorrect value was displayed (05/10/2010).
•	With more than 35 million objects, the application did no longer respond (30/09/2010).
•	If the format of a summary that has already been zoomed is changed, the limitation is cancelled and the values are regenerated in the selected format (10/09/2010).
•	Unnecessary warnings when switching over the format of a numerically derived attribute from string to numeric have been removed (10/09/2010).
•	Reloading data caused a wrong level curve to appear (08/26/2010).
•	When a text file with UTF8-Encoding was imported with the option "Vertical lines are transformed into ¦", the vertical lines were removed instead of being transformed (08/26/2010).
•	In a closed attribute group with blue (focused on a set of values) and red (focused on one value) colored attributes, the color of the header was equal to the last attribute that was focused instead of the red colored attribute (08/26/2010).
•	Closing a table section could result in an exception under certain circumstances (08/26/2010).
•	Format of the Summary "Sum" for an integer attribute is no longer set to "String" when defining a query (08/26/2010).

Release 6.40.6

Improvements

•	Excel 2010 is now supported (08/19/2010).
•	Joins via compound keys in the database wizard were not correctly processed when data columns existed that should not be imported (08/18/2010).
•	Reloading a database wizard template for an InfoZoom join could trigger a warning message under certain circumstances (08/09/2010).
•	Fixed duplicated fields in the database wizard when using the Microsoft ODBC for Oracle driver (06/23/2010).

Release 6.40.5

Improvements

•	Join operations in the database wizard failed when the table name was the same as the name of the join attribute (05/14/2010).
•	Connection data of a data source in the database wizard was not saved when over a certain length (05/12/2010).

Release 6.40.4

Improvements

•	Buttons with icons, like the column headers of the value list, were not always displayed (03/26/10).
•	When several columns were deselected in the designer of the database wizard, CSV-files could not be imported (03/25/10).
•	Fixed an error when importing CSV-files with a large number of columns (03/25/10).
•	Exporting an image from the internal charting component was not possible on Windows Vista (03/22/10).

Release 6.40.3

Improvements

•	When working much with value lists, especially changing the size of the value list window, the program could terminate abnormally (03/11/2010).
•	Pressing the 'Chart' button while a FOP-file was loaded resulted in abnormal termination of the program in the 64-Bit version. Excel charts cannot be used with FOP-format files (03/10/2010).

Release 6.40.2

Improvements

•	The coupling of attributes was cleared when a attribute group was inserted below the coupled attributes (03/05/2010). 
•	Installation of a maintenance release now aborts with an error message if a newer version of the product is already installed (03/03/2010).
•	Undo and subsequent Redo of a Redefine-Attribute-Command no longer results in losing the original values (03/03/2010).
•	Illegible characters are no longer displayed in a cell after redefining attributes with multiple values (03/01/2010).
•	The info field did not contain "Attribute=<anything>" under certain circumstances, even though the tooltip for the selection was "Double click: Zoom-out" (03/01/2010).
•	Resolved problems when opening InfoZoom tables in Windows 7 (02/23/2010).
•	Formatting command has wrongly been reported as not executable (02/23/2010).
•	The query "Who did not retire in a season?" in the Formula One sample table returned a wrong result when executed twice (02/19/2010).
•	When reading schema information from Microsoft Access data sources, the columns were sorted alphabetically in the database wizard. Now they are sorted the same way as in the database (02/15/2010).
•	Connection data for MySQL and Progress OpenEdge databases in the database wizard contained the version number of the ODBC driver (02/15/2010).
•	When a database query in the database wizard required the user to enter a password and the SQL properties have been changed, it was not possible to reload data (02/15/2010).
•	When creating a table section with a subset of the attributes, all queries are copied. If a query contained a command that redefined a classification and the referenced attribute was not contained in the subset, an internal exception occurred (01/14/2010).
•	Office Word Add-In does not report an exception anymore when Word is started from another application (01/14/2010).
•	Queries may be created that try to open a value list for a attribute that no longer exists. When such a query was copied, an exception occurred. For example, this could happen when opening a table section as new table. The problem occurred mainly when creating a table section from a table section (01/08/2010).
•	A query can be set to close all open reports and diagrams when executing. That did not work correctly: When several diagrams were open, only the first one was closed. Also, only the first report was closed. The problem only occurred when no Excel report was open (12/03/2009).

Release 6.40.1

Improvements

•	An incorrect referenced resource caused an exception in the InfoZoom Word Add-In after sending e-mail (2009/11/10).
•	The Button “Date format” in the InfoZoom Word Add-In has been localized in all supported languages (2009/11/10).
•	Updated the Formula One example to include latest results (2009/11/04).
•	Under some circumstances, when carrying only a few attributes over to a table section and there are many queries present that refer to not included attributes, an internal exception could occur (2009/11/04).

Release 6.40

Improvements

•	Faulty string resources corrected (2009/04/29).

Release 6.00.1

Improvements

•	A calculated zero (0.0) occasionally received a minus sign (-0.0). A sign is now never assigned to a zero result (2009/04/17).
•	It was previously possible to modify the vertical lines of multiple values with the “Search / Replace” functionality so that the result was a normal value. However, this could only be done if pattern matching was activated. The notation with vertical lines is really only a syntax for importing text. Permitting this notation in “Search / Replace” caused various problems because the vertical line is also a metacharacter in regular expressions. Also, Undo does not work for these Replace operations. Search and Replace is now only applied to the individual values of a list (2009/04/02).
•	Excel files with long file names could not be loaded if the Excel Wizard was called directly. This problem did not affect access from the Selection Wizard. The length of the file name has now been adjusted to match that of Excel (2009/04/01).
•	As the InfoZoom Protected versions Professional, Business and Explorer have been combined into a single installation, they cannot run simultaneously on a terminal server. The version displayed to the user is determined exclusively by the license key, which is stored in the HKLM branch of the Registry and only exists once on each computer. As a workaround solution, the HKCU branch of the Registry (which exists for each user) is read first when the program is launched; an appropriate license key can be placed there by administrative measures when a user is registered. If a valid key is found there, the license key in the HKLM branch of the Registry is ignored. The HKCU branch is only checked for users without administrator rights (2009/03/31).
•	If new objects were generated by a join and there was a multiple value attribute whose value was then applied to the new object, an error could occur for the first value because a global buffer was overwritten (2009/03/30).
•	If new objects were generated by a join, the corresponding message appeared a little too soon, before an update had been performed. This could lead to inconsistent displays under the dialog box (2009/03/30).
•	When a query was called, the message that some commands could not be executed appeared too soon (2009/03/30).
•	It was previously not possible to transfer queries from a table that contained a hidden attribute. As the hidden attribute could not be transferred, problems arose with queries related to this attribute. This is now permitted, as the queries check more thoroughly whether a command may be executed. If it refers to a non-existent attribute, it cannot be executed and an error message appears (2009/03/27).
•	Under the menu item “Save Objects As…”, the queries were already written to the file and later reloaded. There were some problems with missing attributes here too (2009/03/27).
•	When inserting a table with queries, previously a prompt asking whether the queries were to be transferred was only displayed if all attributes from the inserted table were also transferred. Due to the greater error tolerance now possible, the prompt now also appears if only some attributes are transferred (2009/03/27).
•	When a new object was generated, occasionally an already existing key was assigned to it. This could happen if a Zoom command referred to a value that no longer existed in the table. The value was then included in the list of existing values for the attribute, but the list was not re-sorted afterwards. On generating a key for the new object, the last value in the list was taken and incremented by 1. As the list was not sorted, this could yield an already existing value (2009/03/27).
•	In the context of queries, cases could also occur where an attribute was used as a key although it did not have unique values for each object. As a precautionary measure, the program now checks after executing a query whether it may be necessary to generate a new unique key automatically (2009/03/27).
•	Problems arose with attributes generated by two or more queries. Completion was then invoked repeatedly. It is now ensured that finalization only occurs once (2009/03/27).
•	The SQL code generation properties of the Database Wizard now include an added selection option: “Columns have the table name incl. prefix as prefix”. This supports the connection of DB2 databases via ODBC, where the table schema name must be used to qualify column names (2009/03/26).
•	Enhancements when selecting CSV files in the Database Wizard:
o	Option “No text detection character” now works as expected.
o	When selecting text properties, only the first 100 rows are now read, as only these are displayed in the preview. This speeds up processing of large text files (2009/03/26).

•	CSV files are now read block by block in the Database Wizard, just like the other data sources. Previously, CSV files were first read completely within the .NET environment and then transferred to InfoZoom. This required twice as much memory (2009/03/26).
•	Improved handling of low memory situations in the Database Wizard. Before reading the next data block, the program checks whether a low memory condition applies. A message is then displayed, allowing the user to continue at his or her own risk or work with the records that have already been loaded (2009/03/26).
•	Amendments to the attribute information table and partly the properties dialog: 
o	The “Details” of attributes of types Classification or Case Differentiation were not correctly displayed; the conditions should have been displayed in a vertical list. Display as a multiple value attribute is now ensured.
o	In addition, in Case Differentiation sometimes placeholders were displayed in the conditions instead of attribute names, depending on when the information was accessed. This also occurred in the table properties dialog (2009/02/17).
•	Deleting and moving inactive commands. Because no synchronization took place if changes were made below the insertion point, the subsequent navigation history was falsified. When fast forwarding, unexpected results could then occur. Now the future of the navigation history is also adjusted if no synchronization is performed (2009/02/12).
•	The program terminated abnormally after right-clicking in the blank (lower) part of the attribute column of a .fop file. Double-clicking on the same part of the attribute column (that is, below the last attribute) also caused an exception – this also occurred in normal .fox files. These errors have now been eliminated (2009/01/29).
•	Importing Excel data from additional worksheets (not the first or currently active worksheet) failed. On saving the Excel file directly, it was not taken into account which worksheet was active at the time. Now the worksheet previously selected in the Excel Wizard is set as the active worksheet (2009/01/23).

•	In rare cases, when a file with a temporary attribute generated by a query was saved using "Save Objects As...", an internal exception could be triggered. This interruption resulted in not all queries relating to a table being read. The condition for when an attribute in a saved table becomes permanent has now been changed (2009/01/09).