Using Chronolator Documents
Messages 1000 - 1999
Messages in this range are issued when importing, merging and sorting tables.
1000 | Tables imported |
| All Chronolator tables have been imported. You can merge them into a single table by using the 'Merge Tables' button on the Chronolator toolbar. |
Further Information | Chronolator has imported tables from one document into another. The imported tables appear after those which were originally in the target document. You can continue importing more tables, or merge the tables together. |
1003 | Invalid document |
| The file you chose is not a Chronolator document and cannot be imported into a new Composite Chronology. Please refer to the description of this message in the documentation for suggestions about what to next. |
Further Information | A new Composite Chronology has no information about the requirements for a particular review until you import a Chronolator Document. Once this information is in place, Chronolator will import matching tables from any Word document; but the first document you import into a blank Composite Chronology MUST be a Chronolator Document. |
1004 | Invalid document |
| The file you chose is not a Chronolator document, or it has internal inconsistencies which are described below. It cannot be converted. |
Possible causes | You are trying to convert a document that does not contain the information Chronolator needs, or in which that information has been corrupted. |
1005 | Case References are different |
| Press OK to continue with import, or Cancel |
Further Information | Every Chronolator Document is assigned a Case Reference by the Case Review Administrator in order to warn against accidentally merging documents which relate to different cases. The Case Reference of each document is shown in the message. |
Possible causes | You are trying to import tables from a non-Chronolator document, or from a Chronolator document which has a different Case Reference. |
Possible actions | Press OK if you want to continue with the import, or Cancel if you do not. |
1006 | Cannot import document into itself |
| Chronolator cannot import a document into itself. |
1010 | 'Must-fill' columns are different in source and target documents |
| Press OK to continue with import, or Cancel |
Further Information | Although Chronolator has found tables which have the correct column headings, the 'Must-fill' columns are different. |
Possible causes | You are trying to import tables from a non-Chronolator document, or from a Chronolator document from a different case which has different 'Must Fill' columns. |
Possible actions | Press OK if you want to continue with the import, or Cancel if you do not. |
1015 | No Data Tables found in document |
| There are no tables in the document which match the required column headings. |
Further Information | Issued when you process a document which has no tables with the required column headings. |
Possible causes | If you are checking, sorting, or formatting a document, the table headings might have been accidentally changed. If you are importing a document, the headings in the document you are trying to import do not match those in the composite. |
Possible actions | Check what column headings Chronolator expects, and if appropriate change table headings in the problem document to match the defined headings. You can find the expected headings by using the Admin > Show Document Details button. Alternatively, use the Admin > New Table button to add a table with the correct column headings to the bottom of the document. After you have done so, either copy any data you have already entered into the new table, or copy the heading row from the new table into that of the old one. |
1016 | No events found in document |
| There are no events in the document |
Further Information | Issued when the only Chronolator table in the document contains no events. |
Possible causes | If there is a table that does contain events, its headings have been changed. |
Possible actions | See the suggestions for Message 1015 above |
1020 | Document level mismatch |
| The document you are trying to import cannot be imported into this document as it was created with a higher level of Chronolator. Create and use a new Composite Chronology using the higher level document for this review. Refer to the manuals if you require step-by-step instructions. |
Further Information | Chronolator documents are generally backwards-compatible; that is, newer version documents can read older version ones. However, it is not possible to guarantee forwards-compatibility. |
1025 | Conflicting and Multiple Definitions |
| The document you are trying to import includes some abbreviations and definitions which could be confused with those in this one. Although Chronolator will keep track of what was defined where, reading the document might be confusing. If you want to use the anonymisation / personalisation feature in the Composite Chronology, you must first resolve these conflicts by changing the abbreviations in one of the documents. Press Go To List to review the conflicts, OK to continue with the import, or Cancel. |
Further Information | Chronolator will import a document with conflicting and multiple entries in the Abbreviations Glossary, but if you want to anonymise or personalise the document you must resolve these anomalies. You will be able to do this in the Composite Chronology after import, but it is recommended that you do it in the source document before importing it. |
1026 | Conflicting Definitions - Import Cancelled |
| You have chosen to save the conflicting definitions in a new document. Chronolator assumes this is because you want some time to review them, and will therefore cancel the Import. |
Further Information | Issued if you press Go To List in response to Message 1025. |
1030 | User-defined sequence column found |
The document you are trying to import includes a user-defined Sequence column. It was probably added because the person completing the document wanted to be exact about the order of certain events whose exact times were unknown. Chronolator can either add a Sequence column to the table(s) in this document, or delete the one in the document being imported. Press Add to add a Sequence column to the table(s) in this document, Delete to delete the one in the document being imported, or Cancel. | |
Further Information | Recommendation: Press Add to add a Sequence column to the Composite Chronology so that you can continue to preserve the correct order of events. After you have done so, you can use the Tools > Sequencing menu to add numbers to the remaining events. If you choose Delete, the Sequence column remains in the document being imported but is not carried across. |
1031 | Sequence column not found |
| The document you are trying to import does not include a Sequence column, but is suitable for import in all other respects. Chronolator can either delete the Sequence column from the table(s) in this document, or add one to the document being imported. Press Add to add a Sequence column to the table(s) in the document being imported, Delete to delete the one in this document, or Cancel |
Further Information | Recommendation: Assuming you have deliberately added a Sequence column to the Composite Chronology, press Add to add one to the document being imported (the document itself is unchanged, just the version of it in the Composite Chronology). After you have done so, you can use the Tools > Sequencing menu to add numbers to the imported events. |
1033 | Unable to import |
| Chronolator cannot import anything into this document because of the following internal inconsistencies in its structure: <list of inconsistencies> |
Further Information | The document you are trying to import is a Chronolator Document, but it has some internal inconsistencies. These are listed in the message. |
Possible causes | The internal variables which Chronolator uses to describe the document structure have been lost or corrupted. This can sometimes happen when importing documents across a slow network, or it might happen if Word failed while the document was being edited sometime in the past. |
Possible actions |
|
1050 | Your entry <newPrefix> is similar to the existing prefix <oldPrefix> |
| Chronolator will not use exactly what you entered. You can either import the document using the existing prefix, or you can choose a completely different one. Press OK to use the existing prefix. To choose a different one, press Cancel and then Import Tables again. |
Further Information | Chronolator keeps the list of Source Prefixes tidy. |
Possible causes | Your Composite Chronology already contains information from agency <oldPrefix>, and you are trying to import another document with a similar Source Prefix. For example, If a Composite Chronology already has an agency Berrick New Town Clinic, Chronolator will stop you importing another chronology with a similar prefix such as Berrick Newtown Clinic. |
| 1051 | Invalid Source Prefix |
| The '>' character cannot be used when defining a Source Prefix. Please press 'Import Tables' again. |
Further Information | Chronolator uses the '>' character to separate the parts of multi-level sources. |
| 1052 | Invalid Source Prefix |
| A Source Prefix cannot start with a Author Note tag. Please press 'Import Tables' again. |
Further Information | The characters #, ^, ¬, and ~ are used to identify Author Notes in the Chronolator Reviewer's Tool. |
| 1100 | Tables merged |
| All Chronolator tables have been merged into a single table. You can sort the new table into the correct sequence by using the 'Sort Tables' button on the Chronolator toolbar. |
Further Information | Chronolator has merged all the tables in the document. The next thing you might want to do is to sort the events into chronological order. |
1110 | Cannot merge tables |
| A non-Chronolator table has been found in between the Chronolator tables. The offending table is selected. Please move or delete it and try again. |
Further Information | The document contains more than one Chronolator table, and among them is a non-Chronolator table. |
Possible causes | An ordinary Word table has been inserted by accident. A Chronolator table has had its headings changed. |
Possible actions | If the table contains no data for import, delete it or move it to the end of the document. If the table does contain data for import, correct its headings so that Chronolator recognises it as a Chronolator table. |
1120 | Multiple chronology tables found |
| This document contains more than one chronology table. Press 'Merge' if you want Chronolator to merge the tables and sort them before processing. Press 'Don't Merge' to process each table individually. Press 'Cancel' to return to the document without doing anything. |
Further Information | It is normal to have multiple chronology tables when assembling a Composite Chronology, but in other circumstances it might come about by accident. Chronolator therefore checks how many tables are in a document before most major processes, and if there are more than one it offers to merge and sort them before continuing. |
1200 | Table sorted |
| Events should now be in Date and Time sequence. Some date and time formats can prevent a successful Sort. If that happens, use the Format Dates button to put dates in the all-digital format and then sort the table again. You can put the dates back to your preferred format afterwards if you wish. If you know the order of events on a day but not exactly when they occurred, you can use a Sequence column to put them in order. You can make one using the Tools > Sequencing > Add Column button. |
Further Information | Chronolator puts events with unspecified Times or End Dates before those specified with greater detail if the sort is Ascending, or after them if it is Descending. See Using a Sequence column for details about using a Sequence column. (If the document contains multiple tables, the message heading will be Tables merged and sorted or Tables sorted individually according to the response to Message 1120). |
1201 | Table sorted |
| Events should now be in Date and Time sequence. Some date and time formats can prevent a successful Sort. If that happens, use the Format Dates button to put dates in the all-digital format and then sort the table again. You can put the dates back to your preferred format afterwards if you wish. If you know the order of events on a day but not exactly when they occurred, you can use the first column to put them in order. |
Further Information | Chronolator puts events with unspecified Times or End Dates before those specified with greater detail if the sort is Ascending, or after them if it is Descending. See Using a Sequence column for details about using a Sequence column. (If the document contains multiple tables, the message heading will be Tables merged and sorted or Tables sorted individually according to the response to Message 1120). |
1300 | Dates formatted |
| All dates have been formatted to one of Chronolator's standard formats. If you would like future releases of Chronolator to offer alternative date formats please use the suggestion form on our web site www.chronolator.com. |
Further Information | Chronolator uses two main formats for dates:
The day of the week can be added to both of these formats. If you would like to be able to set other formats, please contact us via our web site. |