The following example (taken from SampleTableWithErrors.docm in the Samples folder) illustrates the sort of errors Chronolator discovers, and shows how you might go about correcting them.
In this example, the Administrator has specified that you can leave any column blank apart from the Date and Source of Information columns.
After Chronolator checks the table, it puts a flag like this ⌧ to the left of any errors and highlights them :
If you hover your mouse over the flag, a brief description of the error pops up. | |
Here, Chronolator warns that it has corrected a row with the wrong number of columns and advises you to check that it has put information under the right headings. | ![]() |
In this example, Chronolator has detected a blank entry in a mandatory column. | ![]() |
The buttons on the Chronolator toolbar navigate from one error to the next: | |
![]() | |
This button takes you to a list of the errors: | |
![]() | |
The list of errors is at the end of the document. Double-click the ⌧ flag to go to where the error occurs. | ![]() |
Error descriptions are preceded by a reference number (e.g. c8n120). If you have difficulty correcting an error, use the reference number to look it up in Check Table Error Codes, where there might be some useful hints.
How you correct errors in a real document will obviously be a matter of judgment. For the purposes of this example, this is what we will do:
The table now looks like this:
Pressing the Check Tables button again results in this:
Many of the problems Chronolator has found are out-of-sequence dates, which it has highlighted in yellow. You could correct these by moving the rows about, or by changing the dates for some events, depending on what is appropriate for the data you have entered.