Release 9.5.0.57 (January 2, 2017)
•After unfolding one of the ribbon combo boxes in the designer, going back to the main window and typing something in the data-edit pane cause a null-reference exception, followed by a crash of the application.
•Check boxes in the data-edit window received keyboard focus twice while tabbing through the controls.
•When updating to a newer version, the settings in the LDAPExchange.ini file were overwritten.
Release 9.4.2.53 (October 3, 2016)
•New registrations were not correctly saved to the database and then disappeared.
•It was not possible to remove photos from the LDAP.
Release 9.4.0.40 (April 4, 2016)
•When selecting an underlined text object, the underline button in the ribbon was not highlighted.
•After closing the properties window, it was not possible anymore to increase the height of the designer window.
•The file-extension drop-down box did not offer the options .jpeg and .tif.
•When running the .NET Framework 4.6 or higher, the combo boxes for selecting fonts, font sizes, border thicknesses as well as the gallery for selecting the content alignment showed as disabled once an object was selected.
•Fields that were hidden from the database-edit window were shown in the record list, even when they were not selected as record look-up field in the database setup.
Release 9.3.0.37 (October 1, 2015)
•When selecting a record with an ID photo that exceeds the maximum allowed size, the image was not loaded, but no error message was shown to notify the user.
•When opening the user-authorizations wizard for a card without database connection, clicking Add on the first wizard page resulted in a new user group being created, but it was not displayed in the navigator and could not be selected for configuration.
•The error “An error happened with authorization data store. If this error persists please contact technical support” could occurred when setting the authorizations for a newly added group or user in the user-authorizations wizard, as a result of previously having deleted a user group.
•When selecting a specific user, rather than a user group, on the last page of the user-authorizations wizard, the error “Your licensed edition doesn’t allow specific user profiles” appeared in the Professional edition.
•Made some improvements for running with larger font sizes.
Release 9.2.2.35 (May 21, 2015)
•When giving a print command immediately after selecting a range of records, it could happen that after printing a couple of cards, the last card of the batch was suddenly printed. It then continued messing up the print order or gave an error that the primary key of the last card in the batch could not be found.
•If the maximum image-size property was changed in the advanced options, it did not take after until after the designer was opened.
Release 9.2.1.34 (May 6, 2015)
•The new-card wizard did not mark the internal databases that are not available in the GO edition as TRIAL when running CardExchange in 30-days Ultimate trial mode.
•When using the LDAP Connector as secondary data source, no LDAP data was shown on the design and trying to process a storage item on the LDAP resulted in a not-implemented exception.
Release 9.2.1.34 (May 6, 2015)
•When quickly switching between templates, the application could enter in a deadlock where it was impossible to select templates or records and where it would not close anymore.
•When opening the designer in maximized mode with the properties window open, the height of the main window was often slightly exceeding the height of the work area of the screen.
Release 9.2.0.32 (March 9, 2015)
•When the selected card had no database connection, opening the user-accounts wizard caused a null-reference exception.
•When printing cards without any objects, commands to move the card to the output hopper were issued to the printer, causing possible printer-busy or time-out errors if not contactless encoding was done.
Release 9.1.2.30 (January 22, 2015)
•When switching templates with text in the name-search box, the error “Cannot change ObservableCollection during a CollectionChanged event.”
Release 9.1.2.29 (December 1, 2014)
•The advanced option “Show service-center errors” was neglected in the main window.
•If the primary key was set to enter manually in the database setup, the typed value was not inserted into the database, causing subsequent database errors.
•When using user authorizations, the level-three filter message at start-up will not be shown to users that are not authorized for switching on and off the level-three filter.
Release 9.1.0.28 (November 14, 2014)
•The auto-print server did not start automatically when setting AutoStart = True in the initialization file.
•When the database-edit window contained a drop-down menu, it was not possible to add a new record unless a value was selected in the drop-down menu. Now, this behavior only occurs if the column was not set as required for inserting and updating.
•When connecting to Excel and setting the primary-key column to Visible but not Editable in the database setup, adding a new record caused the generated primary-key not be stored in the database and the new record not to be shown correctly in the name list (apparently, the previously selected record was duplicated). The work-around was to make the primary key either editable or invisible.
•When pressing the d or n keys in the main window, the Delete and New buttons in the data-edit window were triggered. Now that only happens when pressing Alt+d respectively Alt+n.
•If a combo box had the keyboard focus, pressing F4 resulted in the drop-down menu being shown, rather than opening the designer.
•When closing the card-definition wizard, the drop-down menus in the database-edit window were always marked with a red box, no matter whether they had a valid value or not.
Release 9.1.0.25 (October 9, 2014)
•In some occasions, restoring the window layout resulted in error messages saying that the functionality is not supported.
•On systems with the .NET Framework 4.0, trying to edit a field in the database edit window caused the entire edit window to become disabled, making it impossible to edit update the record.
•In some occasions, the name list showed columns that were not configured as record-lookup columns in the database setup.
•When double clicking on the Properties button in the print dialog, the printing-preferences dialog was shown twice.
•When using a global counter in the mappings for contactless encoding, all cards in a batch except the first one used the previous value rather than the actual one, due to the fact that the value was only refreshed after the contactless encoding.
•After activating a license via the Service-Center ribbon, the message that it will only take effect after restarting the application was not shown.
•When the user authorizations were enabled, selecting a card without database connection resulted in the error “Object reference not set to an instance of an object”.
•After checking the options to use a background picture and a logo in the new-card wizard and selecting only the background picture and not the logo, the Next button was enable. When reaching the end of the wizard, a null-reference exception would occur.
•Without internet connection, nothing happened when clicking the help button, instead of showing the offline help.
Release 9.1.0.22 (September 10, 2014)
•Reset the print counter to zero when a template is imported.
•Solved the error “A 'Binding' cannot be set on the 'Value' property of type 'Setter'. A 'Binding' can only be set on a DependencyProperty of a DependencyObject.” and “Object reference not set to an instance of an object.” that could occur when showing the data-edit window on system with only the .NET Framework 4.0 installed.
Release 9.1.0.0 (September 1, 2014)
•When selecting another card definition, the application sometimes appeared to be hanging. Moving the scroll bar in the loaded-cards toolbar solved the issue. This was a bug in the old toolbar control that now has been replaced.
•When restoring the main window from the minimized state, it was only shown half and the application seemed to be hanging. Double clicking on the window’s title bar solved the issue. This was bug in the old ribbon control that now has been replaced.
•Solved the crash that occurred when trying to print to the Canon Swiftcolor printer.
•After clicking the refresh button in the printer-options window, the first printer was selected instead of maintaining the current selection.
•Removed the data-definition selection area from the card-definition wizard for the GO edition.
•When the database columns had a dot in their name, the following error could occur when selecting a card with storage items: “Value does not fall within the expected range.”
•When importing a version 6 template, no working copy was created, causing file-not-found error messages when selecting the template.
•Typing special characters like the quote symbol in the record-look-up text box caused the error “The expression contains an invalid string constant '."
•When importing a design that was created with a higher edition of the software, some high-end functionality could still be used (variable images, multiple layouts, UV printing, 2D barcodes and background removal).
•When updating old data folders or importing older *.ctp files with cards that were not connected to a database, the following error occurred: “Could not open the data definition from []. No file name defined.”
Release 9.0.8.17 (June 11, 2014)
•When using a filter on records that have been printed already, the printed records were not removed from the name list and after printing the error “Key value […] is not found” was shown.
•When using a database connection and enabling the option “Print card after entering data manually” or “Print card after inserting a database record”, the error “Could not read data from […]. Object reference not set to an instance of an object.” Occurred after applying changes in the manual-entry window.
Release 9.0.7.16 (May 21, 2014)
•When clicking New in the data-edit window, the name-search text box was not cleared.
•The FaceFind options in the photo module were disabled when running in demo mode.
•When selecting a hidden card in the card manager and clicking OK, the software automatically selected a non-hidden card, instead of respecting the selection.
Release 9.0.6.15 (April 10, 2014)
•When the print log was closed when automatic printing was active, it was not possible to show the print log and stop automatic printing anymore.
Release 9.0.3.11 (March 19, 2014)
•When enabling the option import instead of acquire for signatures, the button text was not adapted accordingly.
Release 9.0.3.8 (February 18, 2014)
•Corrected and added some German translations.
•Removed the options in the biometric-options window that were not available in the ribbon.
Release 9.0.3.7 (February 10, 2014)
•When switching from a card without database connection to a card with database connection with the level-three filter enabled, the name list remained hidden.
•Corrected the wrong translations on the first registration page in the German version.
Release 9.0.2.6 (January 1, 2014)
•When the edition did not allow for batch-printing, the print dialog still had the options “All cards” and “Selected cards” enabled, suggesting that multiple cards could be printed.
• Deleting a template in the card manager could cause the manual entries to disappear in the main window.
•MIFARE® Classic and DESFire write items were not correctly shown in the old mappings window.
Release 9.0.1.5 (October 30, 2013)
•To make it possible to print cards without photos in the Go edition, the presence of a photo in the database will not be checked anymore if the photo is not shown on the card layout.
•Arabic, Chinese and other exotic characters did not print nor show on the card preview in the main window, even though they showed correctly in the designer, the name list and the database-edit window.
•After creating a MIFARE® read definition in the designer, the error “Cannot edit the card layout. There is no row at position 0” occurred.
•After creating a new card template the new template was not selected in the main window when running with the logins enabled.
•When running in support mode without a valid license, the activate option in the activation wizard was disabled.
•Corrected some German translations.
