Installation
Most 3di users are in an institutional setting where an IT department manages their computer. Normally, you will need to ask your IT support to install the 3di for you.
If you manage your own computer and have no IT support, these instructions are for you.
IT departments should read the install steps and also the Installing in an institutional setting section before installing.
Windows and Office
The 3di software requires:
Microsoft Windows 10 or Windows 11
Microsoft Office 365
Specifically, you need the Word and Access components of Office to be installed. Typical installations of Office include both components.
Obtain the installer
To get started, you will need a copy of the installer file.
The installer has a filename like 3di5_uk_230122_setup.exe. This filename includes the version number 230122 of the software in yymmdd format, that is year month day. Sometimes you will see a suffix x which denotes a sub revision.
You will receive a copy of the installer file prior to your training course. To find the installer, open the Windows Start menu and type '3di5_uk'. If the installer file is present on your machine, a file name ending in 'setup.exe' will appear in the list. If you cannot find the installer, please get in touch for a new copy.
Installing version 210110 or newer
Run the 3di installer.
You will be asked if you trust the installer file. Say Yes.
You will need to agree to the licence.
Choose the installation folder. The default is your desktop, which is fine for most users.
Click the Install button.
The 3di installer will run to completion and you can click the Close button.
Once the installer has completed, launch the 3di by double-clicking the 3di5_run shortcut on your desktop.
The first time you run the 3di you will have to tell Access that you trust the software. These steps only need to be performed once.
Click OK when you see an error saying that active content is blocked.
When the following dialog appears, click on Stop all macros.
On the yellow bar near the top of the window, click Enable content.
If you have navigated the above warnings correctly, you should now see the Main menu window with 'no backend' loaded.
Continue to Confirming the 3di is working.
Confirming the 3di is working
Open the 3di and navigate to the purple Main menu.
Click Select and open backend.
Choose Training5 with a double-click.
Open the Case Manager by clicking the 🙂 button on the Add-ins ribbon.
Choose any child from the Find: dropdown at the top of the form.
Click the button Report ASD_brief. Within a minute this should produce a Word document. The document may open in the background. If you can't see it, check the taskbar at the bottom of your screen.
Verify that the 3di interview forms will open properly:
Choose Sally Pringle from the Find: dropdown at the top of the Case Manager.
Click on the button Revisit interview on the salmon-coloured central portion of the form.
Opening the interview can take 30 seconds or so on a slower machine, so ignore any early messages about "Access not responding". If an interview form doesn't appear in under two minutes, this may indicate a problem with your Access installation and you should contact support.
Close the 3di by clicking the ❌ at the top-right of the application window.
Installing in an institutional setting
These instructions apply if your computer is managed by someone other than the clinician who will be using the software.
You may find that your computer has administrative policies applied which mean you, the clinician, do not have permission to install the 3di or other software. If this is the case for your computer, please show these instructions to your IT department.
The rest of this section assumes that you are an IT administrator with the necessary powers to install software on the target machine.
Simple installations
If the clinician's machine is a regular Windows installation with their software and documents stored locally on the hard disk (not on a network share), then installation is straightforward.
The contents of the 3di installation folder must be readable and writeable by whichever Windows account the clinician uses to run the software and administer assessments. By default, the 3di installs to the user's Desktop folder, which usually meets this condition. Elsewhere in their user folder is fine too. Installing under Program Files will not work since unprivileged users do not have write permissions for this folder.
In the rare event that Microsoft Access Runtime is present from a prior 3di installation, this should be uninstalled to ensure that Access database files are associated with the most recent installed version of Office, and not the Runtime.
With those considerations in mind, log in to the machine as an administrator, or elevate the session the clinician was running in, then follow the instructions above.
To test your install was successful, follow the steps in Confirming the 3di is working.
Networked installations
The 3di is written in Microsoft Access. As with many Access applications, the 3di is split between two .mdb files, the so-called frontend and backend. The frontend is the part the user double-clicks to load in Access, and contains all of the code. The backend stores patient records. One frontend can switch between multiple backends. During the training course, trainees use the Training5 backend which contains sample data. After that they will create their own backend, and likely never think about backends again, since a backend can store any number of patient records. The usual reason to switch backends is to transfer data between machines or allow collaboration in a research setting.
While it is possible to store the frontend or backend on a network share, our experience is that on slow or laggy wifi with the backend stored remotely, the 3di software can become unusable. Due to the huge diversity of network technologies, in the event of a problem we will usually be unable to help and can only direct you to the Microsoft Access documentation, or your network/remote software vendor's support options.
The installation folder
After a fresh install, the 3di installation folder looks like this:
📁 3di5_uk_230122a ─ Root folder, normally located on user's Desktop
│
├───📁 Backends ─ The Backends folder has one subfolder per backend
│ │
│ ├── 📁 Training5 ─ A special backend with sample data for training
│ └── 📁 MyBackend ─ A user-created backend, normally there is only one
│ │
│ └──📁 Cases ─ User-generated Word reports are output here
│
├── 📁 PreEntry ┐
├── 📁 Reference │
├── 📁 ResearchPapers ├ Must remain in same folder as backend
├── 📁 Resources │
├── 📁 Tools ┘
│
└── ⚒️ 3di5_uk_230122a.mdb ─ The frontend: the main 3di 'program'The default 3di install location is the user's Desktop folder. This is usually the best choice although anywhere the user has write access is fine (so not in C:\Program Files). The user needs to be able to find the 3di5_run shortcut which the installer places on the Desktop. This shortcut simply points to the frontend .mdb file and must be adjusted if you move the frontend after installation.
It is most simple and reliable to keep the whole folder intact. However it is also possible to have the frontend on one drive and Backends folder on another. This might be desirable when patient data must live on a designated drive separate from where programs are installed. To achieve this, move everything except the frontend .mdb file to the other drive, then from the 3di Main menu click Select and open backend and navigate to the new Backends location.
It is essential that all the subfolders of the root installation folder (Backends, Resources etc.) are kept together in the same location relative to one another, or the software will not work.
Placing the 3di folder on a cloud storage service such as OneDrive, Dropbox or Google Drive may cause intermittent problems.
The installation folder is under 100 MB when new. Each new case created by the user typically adds under 1 MB to the Backends folder, including generated reports.
When running from a network share:
A slow or erratic connection to the share will result in a poor user experience.
You will need to tell Access that the frontend file can be trusted via the Access Trust Center. You must tick an additional checkbox to allow network locations to be trusted.
Backends must not be accessed by multiple copies of the 3di running concurrently. This will cause errors and possible data loss. Therefore in a networked setup you must make sure this is impossible.
If you configure the 3di to store its backend on a network drive but that drive isn't available (for example if it depends on a VPN service that hasn't started), the 3di will prompt the user to create a new backend on a local drive. Users may not understand what is going on, and end up being unable to find patient records.
Other notes
After installation, you should go through the steps in Confirming the 3di is working to ensure the clinician has a smooth experience when they first launch the 3di. Hitting a problem in the first clinical session is bad news!
If the machine has Access installed as part of Office, rather than the free Access Runtime, you can perform an additional step to make the 3di easier to use:
With the 3di open, click File → Options → Customize ribbon.
In the right-hand pane, deselect every Office tab apart from Add-ins. This ensures that only the 3di toolbar is displayed, and hides toolbars that are irrelevant.
Click OK to exit. Restarting is not necessary, despite the message which pops up.
It is not possible simply to copy the 3di installation folder to another computer and expect it to work. This is because the 3di installer setup.exe installs dependencies at the system level.
The installer can be run silently (for example as part of a script for use with SCCM or other software deployment tools) and with the installation path set from the command line using the
/Sand/Dswitches respectively. The installer is built using NSIS, therefore the standard NSIS flags are available as documented in section 3.2.1 here.
Last updated