Chronolator logo

The questions below are divided into groups:

Click on an item to find out more about it.

Requirements and Installation

What are the software requirements for Chronolator?

Chronolator 3.4 runs on all versions of Microsoft Word™ for Windows from 2000 to 2016 inclusive, both 32 and 64 bit (where available).

Macros must be allowed to run.

Some restrictions for Word versions prior to Word 2007

Microsoft stopped supporting versions of Word earlier than Word 2007 on April 8 2014, but Chronolator will run on Word 2000, 2002 (XP) and 2003 with the following constraints.

By default, Chronolator uses the .docm format introduced by Word 2007. Earlier Word versions can read and write .docm files if the Microsoft Word Compatibility Pack (available here) is installed, and that is sufficient for 2003.

Word 2000 and Word 2002 (XP) cannot run the macros Chronolator requires in a .docm document even if the Compatibility Pack is installed.

If you need to use a Chronolator Document on Word 2000 or on Word XP, or on Word 2003 without the Compatibility Pack, you should ask whoever sent it to you to send you a version in the old .doc format.

Does Chronolator run on Word for Mac?

Chronolator is designed for and tested on Windows versions of Word.

It will definitely NOT run on Word 2008 for Mac, nor on the Word 2016 provided when Office 365 for Mac was released.

It might run OK on other versions, but it is not tested on them and support is not guaranteed.

Will Chronolator run on Word for Mac in future?

Possibly, but not until Microsoft provide better Mac support for Visual Basic for Applications (the programming language Chronolator uses).

How do I install Chronolator?

See the Installation page.

General Usage

What are the differences between the various versions of Chronolator?

Please refer to the Release History page.

Can you add this or that feature to Chronolator?

Chronolator add-ins allow new features to be implemented quickly by the creation of stand-alone additions which can be attached to a chronology. For example, there is an add-in to produce the timelines required by the Child Practice Reviews introduced in Wales in 2013.

Please contact us at the address on the suggestions page with your requirements.

Known Problems

These are the ongoing issues we have so far been unable to fix or circumvent. Please refer to the Release History page for details of problems fixed in each Chronolator version. If your problem is neither fixed in the latest release nor mentioned below, please describe it as fully as you can in an email to bugs@chronolator.co.uk.

The Sort Tables button sometimes does not work.

This is usually a problem with Word versions and maintenance levels, but might also occur if you have a variety of exotic date/time formats in your document. In either case, format the dates to the ISO date format ("yyyy-mm-dd") before sorting. After sorting, reformat the dates to the one you want.

Word issues message Word cannot complete the save due to a file permission error, and / or a Microsoft Visual Basic error Run-time Error '5487' when saving a Chronolator document.

This seems to be a bug in Word, possibly linked to timing problems between an anti-virus program and something like Google Drive.

Possible circumventions:

  • Try saving again (possibly more than once);
  • Try using 'Save As' and save the document as a different name;

Chronolator Version 3.4 detects this problem and works around it.

Chronolator issues Message 3105 Chronolator table contains invalid rows when importing a Chronolator document, but using Check Tables in the documents shows no such rows.

This is a bug in Word. Force it to rebuild the table by using one or both of the following procedures in the document you want to import:

    1. Type a space in one of the events;
    2. Check Tables;
    3. Save the document.
  • Use 'Save As' to save the document as a different Word macro-enabled document type (either .doc or .docm)

Chronolator Version 3.4 avoids this problem.

I get a Microsoft Visual Basic error Run-time Error '5992': Cannot access individual columns ... when using the Highlight Source or Sequence features.

This is a bug in Word. Saving, closing, and re-opening the document usually circumvents it.

Chronolator Version 3.4 avoids this problem.

I get a Microsoft Visual Basic error Run-time Error '4120': Bad parameter when opening a Chronolator document.

There are two known causes of this error:

  • Your name and initials are not set in Word 2007. Microsoft has accepted this as a problem with certain installations (see this Knowledgebase article).

    Please ensure that your user name and the initials are set up in the Word Options dialog box.

    To do this, click the Microsoft Office Button, click Word Options, enter a user name and initials under Personalize your copy of Microsoft Office, and then click OK.

  • The document is protected with a password longer than 15 characters. Protecting it with a password of 15 characters or less will remove the problem.

I get a Microsoft Visual Basic error Run-time Error '4605': This property or method is not available . . . when opening a Chronolator document.

This problem can occur when you open a Chronolator document attached to an email and Word is set to open email attachments in Reading View. To avoid it, either save the attachment to disk and open the saved copy, or prevent Word from opening email attachments in Reading View by following the appropriate instructions for your version of Word:
  • Word 2003: click Tools, click Options, click on the General tab, clear the Allow starting in Reading Layout check box, and then click OK.
  • Word 2007: click the Microsoft Office Button, click Word Options, clear the Open e-mail attachments in Full Screen Reading view check box, and then click OK.
  • Word 2010: click the File tab, click Options, clear the Open e-mail attachments in Full Screen Reading view check box, and then click OK.
  • Word 2013 and 2016: click the File tab, click Options, clear the Open e-mail attachments and other uneditable files in reading view check box, and then click OK.

I get a Microsoft Visual Basic error Run-time Error: -2147467259 (80004005) Method 'Visible of object 'CommandBar' failed

This has been seen to happen when opening a document in Word 2010 or 2013 and Trust Center settings are such that:

  1. you do not have to explicitly enable macros AND
  2. your document opens in Protected View

You can circumvent this bug in Word by changing your Trust Center settings. There is some information about Protected View and the Trust Center in Appendix A of Using Chronolator Documents.

I get a Microsoft Visual Basic error Run-time Error '5394': This document could not be registered . . . .

The problem occurs if a document is stored in a deeply-nested folder structure that makes the path to it exceed the system limit of 260 characters (see here).

To circumvent the problem, move the document into a folder further up the hierarchy, or shorten the names of the folders in the hierarchy.

Chronolator issues Message 6000 Unexpected Processing Error

Known causes of this message are listed below, together with any circumventions.

Message 6000 when macros are allowed to run automatically and a document opens in Protected View

This has been seen to happen when opening a document in Word 2010 or 2013 and Trust Center settings are such that:

  1. you do not have to explicitly enable macros AND
  2. your document opens in Protected View

You can circumvent this bug in Word by changing your Trust Center settings. There is some information about Protected View and the Trust Center in Appendix A of Using Chronolator Documents.

Chronolator - the chronology tool. Copyright © 2005 - 2017 Berrick Computing Ltd. All rights reserved.

Contact us at enquiries@chronolator.co.uk