Issues

Fixed in Version

•Resolved an issue where silent installs were failing on Windows 10.

•Resolved an issue where text from some eDoc .txt files was not fully extracted due to tab characters.

•Resolved an issue where some email content (more commonly emails with embedded images), fails to display in Concordance Native Viewer.

•Resolved an issue in the Concordance Viewer that resulted in some images displaying backwards when using the Print tool with the color option.

•Resolved a Concordance Viewer issue where produced scrub text files were not output to the correct folder structure.

•Resolved a Concordance Viewer production issue where failed files caused incorrect numbering for other files in the produced output.

10.25

•Header/footer/margin information may be omitted from the produced image of very small files when the option "Fit Image inside of header/footer" is selected in the Concordance Viewer production wizard.

10.24

•Resolved an issue where a record was “Locked for edit” in the viewer when no other users were in the database.

•Resolved an issue where a custom folder name was not created during the Native File production process.

•Resolved an issue where the application crashed if no user name was entered and Apply was selected in the Administration > Security options.

10.23

•Resolved an issue where data in the table view is not automatically refreshed when additional e-documents are dragged and dropped into an existing database.

•Resolved an issue where a previously deleted e-document cannot be re-imported into an E-doc database by dragging and dropping it.

•Resolved an issue where the Concordance shortcut application could be uninstalled while an active database is opened on the workstation.

•Resolved an issue where the starting number in an E-docs database does not increment if the starting number contains more than 20 digits.

•Resolved an issue where additional e-documents could not be appended to an exported E-docs database by dragging and dropping them.

•Resolved an issue where running the Tag to Field feature did not remove tags that were deleted.

•Resolved an issue where the Field to Tag operation does not apply the last tag name if the tag is not contained a folder.

10.22

•Concordance closes unexpectedly when a user tries to use the Create Query feature in the Notes window.

•When selecting specific files to import using the E-Documents import operation and multiple drive tree structures are shown, expanding a single drive tree structure may result in more than one structure expanding.

•HTM files that contain embedded images are not available for viewing from the link in the database record.

10.21

•When tagging records, the Tags pane is not refreshed between query executions when using the Review View and the Split Screen option is disabled.  

•When producing documents, production numbers are written back to the production number field in the database when a record does not have an associated image.

•After changing the admin password, Concordance allowed user to login with both old and new password.

•Send to CaseMap from Query command prompted Concordance to navigate to another record.

10.20

•When performing a Find and a word is not found, closing the Find dialog box and performing another action may cause Concordance to close unexpectedly.

•Numeric field does not accept decimal when working in the Edit view.

•Edit view does not display the Authority List for a .FYI file.

•Navigating between documents is slow when working in the Edit view.

10.19

•When running Concordance in conjunction with document management software, some keyed fields were not displayed.

•Using the Ditto feature caused Concordance to stop functioning if the field data met or exceeded the field's character length.

•Improved performance when creating a CIB file after loading a DAT and OPT file using the Import Wizard.

•Importing HTML formatted emails caused Concordance to stop functioning.

•Bulk tagging documents in the same database simultaneously on two separate machines prompted a message and the bulk tagging function would not complete.

•When importing E-Documents, the Store File Names option, if selected, becomes cleared when the Browse button is executed to create a log file.  Be sure to reselect the check box before proceeding with the import.

•When performing a simple search for Japanese characters (with space between words), search highlights only the first character of the word.  However, if the search is performed on the characters separately without the options "with the exact phrase", "with all the words", or "with at least one of these words" selected, the search returns the expected results.

•Exporting authority lists from the List File Management box, may not export all terms if some of the terms begin with an initial cap and others begin with a lower case letter.

10.17

•Retrieving a large number of tags using the Tagsaver.cpl may cause an Insufficient Memory message to appear.

•Importing E-mails with attachments (.msg file as an attachment) into a Concordance .FYI file, the attached .msg files are saved in the attachment folder of database location.

•(Windows XP) Direct database export from LAW with relative path for text and native files and then running the ImportText.cpt and CreateHyperlinks.cpt pointed to the wrong location.

•Concordance returns more accurate search results when performing a consecutive Simple Search using the "with the exact phrase" option after a previous search for two words that are the exactly same and returns zero hits.  

•The Initial Browse Path field sets the initial folder that opens when browsing for a file or open a new database.

10.16

•Syntax error produced when searching for Japanese characters using Quick Search.

•Kanji characters used in Japanese text not indexing properly on different operating systems (Windows XP and Windows 7).

•No results are displayed for a Date field if no data is present and the field format is set to YYYYMMDD.

•Resolved an issue with the output format of the Edoc import log.

•Incorrect database dictionary displayed for a concatenated set.

•Retention of all fields specified in the Selected fields section of the Import Wizard from the previous import.

•Improved performance for launching a large set of concatenated databases and browsing between the records.

•Resolved the issue when working with a concatenated .FYI file and applying tags to the secondary database in the Table View.

•Using the TRK Maintenance tool in Concordance on a Windows 7 64-bit machine no longer causes Concordance to close unexpectedly.

10.15

•Correct display all fields in the Edit View when using Concordance in conjunction with the Worldox® Document Management application and toolbars.

•Data not loading into the appropriate fields during import for an EDoc database.

10.14

•Words to not printing to a text file when using the Print to File option in the Dictionary dialog box.

•Editing/adding data in the Table View, using the Edit command, did not save the data without advancing to the next record.

•Split screen function in Concordance did not maintain the same location when navigating between records.

•Resolved an issue that removed the .license file from the server when uninstalling a workstation install of Concordance.

•Improved performance when closing the Notes window in a Transcript database.

•Concordance unexpectedly closed during an export of a transcripts database containing more than 40 notes and 9 issue tags on the same record for a .pcf file.

•Files were prevented from loading when attempting to load a non-Unicode .DAT file that contains a Unicode character in the header row.

•Printing fields using KWIC with more than 500 hits, all fields were printed instead of the selected fields.

•Additional metadata getting appended to the bottom of the TEXT01 field when importing PDF files.

•Updated the user interface to initially display fields in the Available Fields list instead of the Selected Fields list.

•Landscape print orientation is not persisted in the Print Setup dialog box.

•File > Print command printed all the pages of a document instead of the specified page range.  

•Resolved an issue where Concordance would not open a native hyperlink if the filename contained any punctuation characters.

•Resolved the issue where Concordance closed unexpectedly if tags and folders were created in the Tag and Issue Management dialog box using Non-ASCII characters, smart quotes, or an em dash.

•Resolved an issue that resulted in an incomplete import of OCR text when using the ReadOCR_v10.06.cpl.

•Resolved an issue that caused the ReindexingDaemon.cpl to stop unexpectedly and close the database.

•Resolved an issue where a text file containing a punctuation character did not load when using the ReadOCR_v10.06.cpl.

•Resolved an issue when using the EDocView_v10.00 cpl opened the last page of a PDF document instead of the first page.

•Resolved an issue where a blank Date field is not highlighted when Editing data and navigating between records in Concordance.

•Resolved an issue that did not allow wildcard characters to be used in the Stopwords list.

•Resolved an issue that caused hit highlighting to apply to all text instead of the specified term when viewing records with IPRO.

•Resolved an issue that resulted in the TextFileToQuery.cpl skipping text that contained more than 127 characters in a single line.

•Resolved an issue that resulted in the page count for multi-page documents did not appear in the TEXT01 field of an E-Docs database.

•Resolved an issue that triggered a warning to display every time the Send Fact To CaseMap command is selected even though the Don't show this dialog again option is selected in the warning dialog box.

•Resolved an issue when exporting to a Delimited Text File, the Export in ANSI format option, if selected, became cleared when the Browse button was executed to create the DAT file.  

•Resolved an issue that produced an error message when attempting to use the Tally command in the Browse and Edit view.

•Resolved an issue where the Global Replace for a date field did not execute properly.

10.13

•Resolved an issue where running concurrent opposing bulk tag operations may result in a locked TRK.

•Resolved a normalization issue where the import process for ASCII and ANSI text files resulted in files that were not properly indexed.

•Resolved an issue where concatenated databases that contain similarly spelled named tag folders appeared as separate folders.  Tag folders that are differentiated only by case are now shown as a single folder.  For example, database A contains a Client folder and database B contains a client folder.  When the databases are concatenated, a single Client folder is displayed.

•Resolved an issue that produced an error message when attempting to use the ConvertDatabaseAndImageBase CPL to convert a database that is not open.

•Resolved an issue where a tag query produced empty records in the query results for records containing the named tag and the records were previously removed from the database after packing the database.

10.11

•Improved performance when navigating between documents.

•Improved performance when importing and exporting users using a comma-separated file (.csv).

•Resolved search hit highlighting when using the with the exact phrase option in the Search panel.

•Resolved an issue when importing attachments that contain different content but identical filenames.

•Resolved an issue that caused Concordance to hang with loading multiple transcripts larger than 12MB.

•Resolved an issue where some Unicode formatted .msg files would not import into Concordance E-Documents database and do not retain rich text formatting.

•Resolved disabled navigation buttons in Concordance when an email attachment link is executed within an e-mail database.

•Resolved an issue that required administrator rights to run full version of Concordance when locally installed.

•Resolved an issue that did not allow an administrator to disable the Convert to Single Database menu item without a database open.

10.09

•Resolved performance issue in Concordance when sorting a large number of records.

10.08

•Improved performance for record to record browsing when using Concordance to directly access a database containing a large number of tags and folders.

•Resolved a performance issue in the Concordance – CaseMap integration, when linking records from CaseMap version 8.5 to Concordance version 10.05. Links to Concordance now return a single record.

•Resolved an issue where a Unicode character added to a tag query did not return any records.  Users now receive a message indicating unrecognized characters in the tag name, and can make the tag name corrections.

10.07

•Resolved the write() CPL function that is used in the ExportOCR.cpl so it will export Unicode when present instead of just ANSI.

•Resolved the opendb() CPL function so it will again open databases listed as menu items and that have security enabled and access to create new databases disabled.

•Resolved an issue that was introduced in the 10.05-only version of the Concordance exit() CPL function to again properly close the Concordance application.

•Resolved an issue so Snapshots files (.snp extension,) saved in pre-version 10 databases, can now be restored and displayed properly in the Review pane after the database is converted to version 10.

•Ensured that, when installed, “Concordance 10”, “Concordance” (v9), and “Concordance 8” will always appear as Windows right-click “Open With” menu options to open a .dcb file regardless of the order in which Concordance versions (8,9, and 10) have been installed on the workstation.  Also when installed none of the versions will automatically change the workstation’s Windows file associations.

•Resolved an issue, introduced in the last build, which can be encountered only when using the Concordance and CaseMap® integration, with records linked between the applications and using a Concordance database that has had records deleted from it. This then could cause the link-back feature from CaseMap to retrieve and display the wrong Concordance record. This is a software-side-only repair as no data was affected nor were the database links between the two products.  By installing the build above this workflow will again function properly with no additional client action required.

•Adjusted CPL paragraph and buffer sizes to ensure that text will properly overflow after every 12MB loaded from e.g., OCR1 to OCR2 to OCR3 and beyond as necessary when using the ReadOCR_V10.00.cpl, ReadOCR1_V10.00.cpl, READOCR1 (single page)_v10.00.CPL, and LoadOCRFromOpticonLog_v10.00.cpl.

•Resolved an issue that was preventing the .dir and .vol files from being created when exporting from CloudNine™ LAW when the "Automatically Load Opticon Imagebase Files" option is chosen in the LAW Export Utility.

•Resolved a display refresh issue where, after performing a search in Simple Search > with the exact phrase, one would see hit results in the Table and Review panes but would see the message “No Documents Found In Query” in the Browse view until that pane was clicked on.

10.06

•Resolved an issue for full-text (indexed) searching that occurred only with some repetitive word strings like "aloha oe aloha oe aloha oe". Now portions or exactly all the text in these types of longer repetitive word phrases are indexed properly and will be returned as search hits.

•Made the List File Management > Export of the contents of .TRK files work the same in Concordance version 10 as it does in version 9.5x. It now exports all the entries (#, $, +, -) instead of only the # entries.

•Resolved an issue where the using the search operator “co” (contains) in the Quick Search bar would return, in addition to the expected search hit, hits for the empty date mask value "00/00/0000" in Date-type fields, even if a different search string was searched for.

•Corrected the behavior of the “Default” user when the “Enable security” and “Logon required” check boxes are both selected on the Field rights tab in the Security dialog box to allow the rights that were assigned when working with concatenated databases outside the “main” database.

•Resolved an issue to again allow the Right-click > View image command in the Table View to launch the image in Concordance Image.

•Repaired the CPL function 'OpenDB' so it can be used in custom CPLs to open and create new databases without leaving menu items disabled.

•Resolved the text in the “OCR Indexing” warning dialog box so it is no longer truncated and now fully tells users how to turn off OCR Indexing under File > Modify for Concordance version 8 databases that get converted to version 10.

•Resolved an issue that was allowing restricted menu items that were disabled using File > Administration > Security in a database opened in one tab to then be displayed if the same database was opened again in another tab during the same session.

•Certain file types that are encrypted or cannot have text extracted e.g., .RAR, .ZIP, or .EXE can now be imported into the database directory and have a record created for them when using Documents > Import > E-documents.

•Resolved an issue where disabling the Workspace tab using Tools > Preferences > General was graying out the Convert Single Database menu selection.

•Resolved an integration export issue in CloudNine™ LAW, when performing Concordance Direct Exports from LAW, where Unicode characters were inserted in place of ANSI characters in Text format fields.

•Resolved an issue where heavy bulk tagging followed by bulk untagging of very large record sets and then exporting as a Concordance database could result in a tag still appearing as tagged to a record.  If however, the tag was unchecked or untagged by normal means, the tag would not remain tagged after the export.

•Extended the path length allowed for file paths longer than 135 characters when browsing to locations in File > Administration > Add Menu Items.

•Resolved an issue that was preventing the FindAttachments_v10.00.cpl from returning new results if run more than once in a row without first creating a new tag to base it on or reopening the database.

•Resolved an issue that was preventing users with the Editor security rights from seeing the list of available fields when the Ditto function was used to copy records in Edit mode.

•Resolved an issue to allow more than one menu item to appear after adding the entry [DeletedMenuItems] in the Concordance.ini file and adding two or more items.

•Resolved how the .dat file import function reads the file headers of certain ANSI format files to ensure they also import properly.

•Resolved the concatenation of two databases where the “Enable security” check box is selected but the “Logon required” check box is not selected on the Field rights tab in the Security dialog box.

•Resolved a refresh issue when a tag is created and then a query is immediately created from that tag, a message appeared stating "No documents found in current query".

•Resolved a transcript loading issue where transcripts with their first line empty can now be loaded.

•Resolved an issue where when applying a tag to a record and then immediately performing a Form Search, the first record displayed in the query appears to have that same tag applied to it.

•Resolved an issue where clearing all the "Sticky" check boxes in Tools > Preferences > Viewer causes Concordance Image to not open when clicking the camera button in Concordance.

10.05

•Some clarification was added to the Security Logging .csv output file. When the user clicks on a button or checkbox that changes a security setting, that change is logged and then when the changes are saved, a "ChangesSaved" event is logged.

•Resolved an issue that was preventing Send to > Excel from sending all records when records from multiple concatenated databases were chosen to be sent to Microsoft Excel®.

•Resolved a .dll call issue that only occurred on some machines, where after adding punctuation in the File > Modify Punctuation field, none of the punctuation would then be displayed in that field.

•Resolved an issue that caused a “disk full” message to appear when a Reindex was run and more than one user was logged in to the database.

•Resolved some issues in the communication of startup and shutdown processes between Concordance and Microsoft Office Messaging API (MAPI). This fix improves stability when importing Microsoft Outlook® email .pst files.

•Resolved an issue that was preventing the CPL function “snapshot” from working properly when using it to restore a Snapshot (.snp file).

•Resolved an issue with the CPL function “PutFieldEX” that was preventing it from properly writing to the database.

•Resolved control logic to Send to > Excel where the HKLM\SOFTWARE\Classes\Excel.Workspace key is missing from an install of MSOffice as when it is installed on a Citrix Presentation Server. The process correctly handles a failed registry lookup and displays a dialog box prompting user to first open Excel so the “Send to” operation can complete.

10.03

•Resolved several issues in the Concordance COM interface that cleans up the communication with partner applications like EL Native Review for Concordance.

•Resolved an issue with converting databases to version 10 where when tag names contained the single quote (‘) or double quote (“) were creating a message stating “Error in prepareSql near “s”: syntax error”.

•Resolved an issue where some Unicode™ UTF-8 text and .DAT files were not importing properly due to missing file header identification. File identification is now performed differently to detect these file types.

•Resolved an issue where setting the viewer preference to the internal viewer in FYI Reviewer would also mistakenly set the Concordance viewer preferences to Internal.

•Resolved a refresh display issue in the Tags pane when a user created a new tag, performed a Form Search, and then returned to the Tags pane.

•Resolved an issue with the CPL Function OpenDB() where it was improperly restoring database pointers after the CPL ran and sometimes disabled the menu item.

•Resolved a buffer size allocation error that could occur in version 10 Unicode databases with the CPL Function:  Cplcreat.c IndexArray().

•Resolved some issues with CPL Functions Keep() and Exec() and their handling of Unicode.

•Resolved an issue where search terms were sometimes displayed as truncated in the Search Review display after running a Tally. The search terms now display properly.

•Corrected an issue where empty but persistent tags that had no records tagged to them in version 9 would get dropped when the database was converted to version 10.

•Resolved an issue from Concordance version 9.58 and FYI Server 3.53 where Issue Tags were not immediately synchronizing from being made in FYI Reviewer to being viewed in Concordance.

•Resolved an issue where when the Edit Mode is displayed on top and the Table View is displayed on the bottom and multiple records are selected from Table View, only the current record being displayed in Edit Mode was sent to Microsoft® Excel® when the user right-clicked and tried to send all the selected records in the Table View to Excel.

•Resolved an issue with importing Hex symbols 92, 96, 99 and 85 using the ReadOCR_v10.00.cpl.  These High ASCII characters were not being properly interpreted for Unicode conversion.

•Resolved an issue in Transcript template databases when using the Go To button to navigate to a specific page and line number it was retaining the last navigation selection and not advancing to the desired location.

•Resolved an issue with some data sets where exporting a .DAT file as ANSI could combine records without properly including the hard return character.

•Resolved an issue that could occur with some Rich Text formatted emails that are imported in to Concordance.  In some cases, when exporting these types of records out to a .DAT file text, the extracted email text was being truncated when viewed in the .DAT file.

10.02

•Resolved an issue where conversion of some databases to v10 results in non-English Unicode characters.

•Added a dialog box so users will be reminded to back-up databases prior to single database conversion.

•Import and Export of delimited text now allows for ASCII characters 28-32 as delimiters

10.01

•Resolved a Concordance install issue where the activation dialog could not be automated using the “silent install” functionality. Instructions for a silent install can be found in the Concordance Installation Guide.

•Improved the warning that data might be lost when modifying a database structure. The warning message now provides more details.

•Word and Edit lists can now be opened from the Edit menu (Edit:Lists:Word Lists or Default List).

•Resolved an issues with keyboard shortcuts not working in some cases when switching between views.

•Resolved an interface issue where the increment and decrement arrows did not work in the Widows and Orphans fields on the Report Wizard – Printer dialog.

•Resolved some issues where keyboard shortcuts from one view would remain active when a different view had focus. Sometimes this behavior is appropriate but several inappropriate cases were Resolved.

•Resolved an issue in the Annotation Report writer where the issue list would not print if it was the only thing chosen to print.

•Resolved an issue where character size would "explode" in size making the screen unreadable.

•Resolved an issue where the Print button in Print Preview would not bring up the printer dialog.

•Resolved communication issue between Concordance and Concordance Image when multiple databases are open in Concordance. Prior to this fix, if multiple databases were open in Concordance, then Concordance Image would not change to the proper imagebase when a user changed database tabs in Concordance.

•Users will now receive a warning if they try to create a new field with the same name as an existing field. Prior to this fix, the new field was not created and no reason was given.

•Users can no longer uninstall Concordance while the application is running.

•Resolved an issue where appending multiple production number sets to a single field data would appear in the incorrect fields in Table view. This was a refresh issue.

•When used in conjunction with FYI Server version 5 Concordance 10 will display a warning dialog when the connection to FYI Server is dropped.

•Quickmarks now display in the Notes pane on the Navigation pane.

•In the File > Modify dialog, the Print button was renamed to Save To File because pressing the button saves a text file containing the structure of the database. The file is now also saved with the .txt file extension.

•Changed the license file that is saved at activation time to remove the dependency on the Microsoft Windows encryption DLL.

•Resolved an issue where attachments on notes could not be saved using the “Save attachment as” button. Previously, the file was not saved and no message displayed.

•Resolved an issue where a note could not be edited if there was highlighted text in the note.

•The F1 keyboard shortcut now opens Help even if there is no database open.

•Resolved an issue where a second user could not go to a record that was being edited by another user.

•Resolved several issues when a user tries to print or print preview with no printer installed.

•Resolved an issue that caused "Tally on a tally" to not be available sometimes.

•Resolved an issue where a user received a cryptic message if the .Layout file or the folder containing that file was read-only.

•Concordance no longer creates a Concordance.ini file in the C:\WINDOWS folder.  When installed on a Windows XP machine the items tracked in this .ini file are now tracked in the Concordance_10.ini file in C:\Program Files\LexisNexis\Concordance 10.  When using Microsoft Windows Vista® however the Concordance_10.ini file is created in C:\Users\username\AppData\Local\VirtualStore\Program Files\LexisNexis.

•Focus issues with some views were Resolved. For example, when first opening a database, the workspace for that database now gets focus.

•Resolved an issue where only the first field in a field group would be successfully searched. Field groups are set up in the database's INI file using this format:

•When searching, use the alias rather than writing out all the different fields.

•Improved behavior when trying to run the same search twice. The search will now execute if search history is cleared or switch database tabs. It will not execute if there is an attempt to run the same search twice in a row on the same dataset.

•Resolved an issue when building queries using Advanced Search. When using the database dictionary to select words from the list, the words would be inserted with a space between the left parenthesis and the word. This was syntactically incorrect and needed to be corrected manually to run the search.

•Resolved an issue where clicking the Cancel button more than once while indexing or reindexing caused multiple dialogs to open. Some of these dialogs were displayed behind the Concordance window. The confirmation box now only appears once, even if the Cancel button is clicked more than once.

•Users will now receive a warning when trying to reindex a database when they do not have sufficient Microsoft Windows privileges to modify the .dct or .ivt files.  Prior to this fix, the reindex failed without an explanation. The new behavior matches the existing behavior for indexing.

•Resolved an issue where a newly created e-mail database could not be edited until after it had been indexed at least one time.

•The indexing and reindexing status dialogs are now modified to prevent users from attempting to perform other actions while indexing or reindexing.

•Resolved an issue where giving a field the indexed property while modifying a database did not set the Reindex needed flag in the File menu.

•Removed an incorrect statement from the Help system. In the early versions of Concordance, relational searches were limited to the first 60 characters of a paragraph field. When this limitation was removed from Concordance, the Help file was not updated.

•Significant updates about replication were made to the Help and Concordance User Guide.

•Added warning dialog to remind users that only the primary database in a concatenated set can be synchronized.

•Resolved a refresh issue when resolving collisions for documents with tags.

•Resolved refresh issues when the Done button is clicked after replication. New tags are now displayed properly.

•Following a synch back to the subscriber, removed issue tags were not removed from the replicated database. This was a timestamp issue. In this scenario, the removed tags are now removed from the replicated database.

•Resolved multiple issues with the Save Settings button not saving some settings.

•Resolved an issue where some tags were not properly created when a replica of a database was created.

•Resolved cases where the dialog for resolving conflicts with notes would not display.

•The “Publisher overwrites” button in the Subscriber section of the Resolve note collisions dialog is now renamed to “Subscriber overwrites”. In an earlier version of Concordance, this button had the wrong label.

•Resolved the ‘G’ and ‘D’ (Go to Document) keyboard shortcuts on the Collisions dialog.

•The Serial number field no longer has an edit box on the Enable Replication dialog. The field was always read-only and any changes entered into the edit box were discarded.

•Resolved an issue where the Conflict Manager dialog would not close under some circumstances. The Conflict Manager dialog opens when synchronizing databases after changes are made to a replicated database.

•If a user is searching in a concatenated database set where one or more of the secondary databases are not indexed, they now receive a more meaningful warning message that indicates some databases are not indexed.

•The Reindex flag in the File menu is now displayed if any database in the concatenated set requires indexing.

•The Empties checkmark on the Tools menu is now updated based on the current database being viewed in a concatenated database set.

•Added messaging to inform users that to use certain options such as Overlay and Export with concatenated databases require that the DB structure and field names are the same across the databases in the concatenation.

•Resolved an issue where the reviewer received an error if a concatenation set had images in some databases but not in the first database.

•Resolved an issue where the reviewer received an error if a concatenation set had an .sec file in some databases but not in the first database.

•Security is now normalized across a concatenated set. The new security methodology is described in Concordance Help in the “Security Guidelines” section of the “File:Concatenation:Concatenate” topic.

•Setting up security for concatenated databases includes the following guidelines:

•Security settings need to be set up in each database. Setting security in a concatenated database set only affects the primary (first) database.

•The user name and password must be the same for all databases in the concatenated set when security is enabled.

•When the user name and password in the primary database does not exist in a secondary database, and security is enabled, the concatenated database will not open. The user will receive a message that they do not have access rights to the specific database.

•When a secondary database has security enabled and the primary database does not have security enabled, the user is prompted for the user name and password when using the secondary database. The user name and password entered becomes the user name and password for the concatenated database set.

•Concatenated transcript databases now display the database’s name, date, and time in the title bar.

•Resolved an issue that prevented printing across the concatenation line when multiple transcript databases were concatenated.

•Changed how menu items appear when several DBs in a concatenated set have the same menu item.  These menu items now are only displayed once instead of repeating duplicate menu items.  So for example if a CPL like TagToField_v10.00.cpl listed as a menu item in five concatenated databases this menu item will display only once instead of being displayed as five separate instances.

•Resolved an issue involving File > Send To > Excel.  Now all records that are selected in Table View from different DBs in a concatenated set will be sent to Excel regardless of the order these records were selected by the user.

•Resolved an issue where matching with multiple fields would not find matching records and would append all records to the end of the database.

•Resolved an issue where the file extension selected by the user was not automatically appended to the filename.

•By default, the “Export rich text” check box is now unchecked on the Export Wizard – Fields dialog for exporting to a delimited file. This functionality now matches the field default on the Export dialog for exporting to a database.

•Now when a document with no "body" is imported, a record is created that holds the metadata and a link to the document. Examples of documents with no body are Microsoft Excel charts, .jpeg files, some .pdf files, and some ACAD drawings.

•When importing a transcript larger than 10 MB, a warning is now displayed that the transcript will be truncated.

•In previous versions of Concordance, when very large Microsoft Excel spreadsheets were imported, there would sometimes be strange behavior such as the user being prompted to save a text file. This has been Resolved.

•Concordance now imports hidden Microsoft Excel worksheets.

•When importing e-mail and attachments, Concordance now creates a log with details about messages that fail to import.

•Now select the .fyi and .pdf file types from the “Files of type” field on the Open dialog on the Added Menu Items dialog.

•Updated the preset menu items for user roles to include the new menu items.

•When a menu item is restricted in a menu, the menu item function will no longer be available in other parts of the interface. This includes the Navigation pane, right-click menus, toolbars, and keyboard shortcuts.

•The View:Toolbar:Toolbar menu item is now renamed to View:Toolbar:Standard.

•Resolved a Browse view refresh issue when using .fmt or .arp files as added menu items.

•Added the View> TableView >Table layout menu item to the Menu access tab on the Security dialog. The Table layout menu item can now be removed from a user’s menu.

•Resolved the ReportFS() CPL function so that it spawns an instance of Report Writer as expected.

•PrintWithAttachments_v10.00 CPL now correctly prints the parent document and the attachments. Previously, only attachments were printed.

•Updated the comments for the BlankField_v10.00 CPL to include the warning that it is only valid for Text and Paragraph fields.

•Resolved an issue where incorrect icons were displayed in the Navigation pane of the Workspace tab after running CPLs.

•Removed the SendToExcel CPL because this functionality is also available in the Concordance interface.

•Start.CPL will execute when Concordance is started. The CPL must be in the same folder as the Concordance10 executable file. Start.CPL does not follow the CPL naming convention that includes the version number due to the nature of this CPL. For more information about the Startup.CPL, see the Concordance Help or the Concordance User Guide.

•Significant performance improvements for the following tagging operations:

•Deleting a tag

•Multiple users simultaneously bulk tagging

•Resolved a time zone issue that would cause tag statistics to appear inaccurately depending on the time of day and time zones where tags were create and the time of day and time zone where the statistics were viewed.

•Resolved an issue where a tag added on the Tag and Issue Management dialog could not be deleted until data was imported into the database.

•Resolved an issue where personal tags inside nested folders were not always tracked by tag history.

•Improved the interface for the Delete Tags confirmation dialog. The confirmation dialog is generated after clicking the Delete button on the Add/Delete tab of the Tag and Issue Management dialog. Previously, parts of the interface could extend off the bottom of the dialog if many tags were being deleted.

•Added New > Issue to the right-click menu of the Tags pane when text is selected in the Browse pane.

•Resolved an issue when more than one database is open and switched between them after running tag statistics, the statistics from the first database would appear for the second database.

•Resolved an issue where personal issues were viewable by other users in the Notes pane.

•Resolved an issue where the Tags pane did not refresh following an index or reindex.

10.00 and earlier

•When using the Field to tag option, it does not apply the last tag name only when the field selected appears after the OCR numbered fields.

•When working with an exported E-Documents database, the drag-and-drop operation for appending new documents causes the near native file import to fail.

•E-Documents import log file lists failed extraction message for a .docx file that does not contain any text and the file is not viewable in Concordance Native Viewer.

•Changing or renaming media keys prevents Concordance from executing a Native File production; however, the documents are still displayed in Concordance Native Viewer.

•After deleting a record and packing the database, and then attempting to add the document back to the same database using the drag-and-drop operation, produces a message stating that the file already exists.

•When creating an E-Documents database, choosing to map the file path data to a field other than the FILEPATH field does not display the file path as a link in the database.

•Images that are originally set up as "Fit to Width" are not properly processed when imported creating an E-Documents database.

•Data is not imported when the ReadOCR CPL is executed on a text file that contains a single character.

•The PrintPDF.cpl is not included with an E-documents import.  Please contact Concordance Technical Support for a resolution.

•During a Native File Production, a blank text file may be produced if the file name contains any Unicode character.

•The drag-and-drop operation does not work as expected when adding documents to an E-Documents database if the database contains any system fields.  For a resolution, see the System fields improper field rights item in the Information and Error messages topic in the Concordance Answer Center or contact Concordance Technical Support.

•Header and footer information is not captured in the OCR of a record and is not imported for Microsoft® Word documents when performing an E-documents import.

•Concordance may stop functioning after applying a quick mark to a transcript and then attempting to export the transcripts database.

•After renaming a table layout in the Table Layout dialog box, all available fields are displayed in the Table view and the new table layout name is not retained.

•Disabling the workspace and then attempting to perform a single database conversion of a Concordance version 9 database may produce an error message and inaccurate data in the database.

•(Windows XP only) When using the Uncheck Issue command in the Tags pane menu for an issue that is applied to multiple notes in a record, an error message may appear and cause Concordance to close unexpectedly.

•Menu items are disabled after setting access limitations even before setting up security for the database.

•When using the Import Wizard to create a database for use with Concordance Native Viewer, importing OCR text and not importing the OPT file, creates an empty CIB file.

•Performance may be slow when exporting a Concordance database that contains a complex tag structure.

•When converting a Concordance version 8.x database to a Concordance 10.x database, if the database contains a tag(s) with the ampersand (&) or pound (#) character in the second character position (i.e. a#Weller) an extra tag is created (i.e. #Weller) in addition to the existing tag.

•Menu access rights are not captured properly when importing a security (CSV) file.

•With the workspace disabled, no message is displayed denying access to the database when attempting to login to a .FYI file after entering a username and no password.

Concordance Desktop