Question and Answers
Q1. Trust Location Issues
A.1. The Trusted location is a Microsoft security feature. This is set by the installation programme; thereafter moving the data files is handled by a re-linking routine within the application. Moving the programme file may cause trusted location issues. Users with the full MS-Access programme can simply add the new directory to their trust locations. However, those users running the application from the free runtime module are reliant on the trusted location being set during the installation process.
Your data will be safe provided you have not un-installed any on the applications?
Your data is contained in the following file;
This file can be located in the data directory under the parent folder.
Copy the files to a safe location.
Un-install and re-install the programmes. Copy the file above back into the data folder over the newly created file from the installation.
Should you have lost the above file it may still be possible to recover your data had you run a backup from within the programmes? Under the data directory you will find a folder containing up to a maximum of 3 files. The date and time the backup was made is recorded in the backup mask – for example “TIRABkp - YY-MM-DD HH-MM”. If necessary you could take the most recent backup and simply renamed it back to its original name (see above) and again copy it back to the data directory.
Q.2. Error Message : Read-Only This database has been opened read-only. You can only change data in linked tables. To make design changes, save a copy of the database.
A.2. This problem will occur when sharing properties do not "Allow user to Read/Write files"
Try to "Run As Administrator" either by right clicking the short-cut or modifying the short-cut Compatibility, Privileged property. If your using a works machine your IT support should be able to place the application on a directory that allows read/write access between the front-end Graphical User Interface and the back-end Data-container.
Q.3. Can I email reports and risk assessments
A.3. TIRA has no direct method of emailing reports or risk assessments. However, users can when selecting the 'Print Option' ribbon (available on far right only when a report or assessment is being viewed) select the print menu button, and then by changing the name of the printer to either PDF or XPS save the file to their PC. The saved file can then be e-mailed in the normal manner.
Note the PDF and or XPS choices will be dependent on what options have been install on your machine.
Please bear in mind that risk assessments saved and emailed using this method may not show the all important acceptance and sign off signatures.
Q.4. Can TIRA be Used over a Network
A.4. The quick answer is yes. That said, much will depend on how your company network is set-up as to how well TIRA will function. TIRA was developed on a standalone system but programmed and designed to be network friendly. However, we were unable to do extensive testing in a network environment.
Basically, all you need to do is have a copy of the front end GUI on each user’s terminal (TIRA_v#.accde). This can be achieved running the standard setup file to install TIRA on each machine. The installation will link TIRA’s front-end to its back-end data container file for each PC it is installed on. What you need to do then is to move one of the TIRA_be.accdb back-end files to a network location where all users can access it, and then delete all the local TIRA_be.accdb files. When you start TIRA the programme will notice that the back end file has moved and prompt you to help locate where the file has been moved to (your IT may need to do this). Simply do this on each machine TIRA is installed on and run some tests to see how the programme performs from the various locations and with different users accessing TIRA at the same time, etc.
Please ensure that TIRA has full read / write permissions for the directory the front-end and back-end files have been moved to otherwise you will receive error messages stating that TIRA has been opened in Read-Only mode. (see Q2)
Q.5. Will TIRA work on a 64Bit PC?
A.5. Our software is designed to run in a 64 bit environment, however as is utilises MS Office 32 bit runtime components, it will not run on PC installed with 64 bit MS Office 2013. This is because Microsoft will not allow both 32 bit and 64 bit runtime files to operate in the same environment. This is not a 64 bit PC issue as our software was developed on a windows 8.1 64bit PC, this is merely a limitation within the MS Office packaged that Microsoft has introduced.
From our perspective it makes more sense to distribute our applications in 32 bit, this as for the best part they will run on both a 32 bit and 64 bit PC. Microsoft recommend customers should install the 32 bit office version, this unless they have very specific reason for using the 64bit version, for example spreadsheets or databases over 2GB in size.
Q.6. How do I obtain an unlock key / register my application?
A.6. Unlock keys are issued on receipt of the program’s padlock number. As each PC will produce a unique padlock number, it is for this reason we are unable to issue an unlock keys until we receive the padlock number.
The padlock consist of 4 rows of alpha numeric characteristics and is offered each time the program is run. The program offers a semi-automatic registration system to assist in unlocking the software.
Q.7. Why has the program loaded the re-linking routine form?
A.7.The re-linking routine normally only appears on non standard installations, i.e. networks or for XP pre SR2.
The programs expect to find their data in the default installation directory on C: Drive. If not found, the semi-automatic re linking routine is loaded to assist the user in locating the source of the data containing files. (Not every PC will have a C: drive)
Here is a link on how to use the semi-automatic re-linking routine for our TIRA application, the principal is the same for all our applications (hosted in Youtube).
On Safe Lines QHSE Software Help file v7.1.03 : Copyright © 2003-2019 On Safe Lines QHSE Software Ltd