Question and Answers
Q.1. 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.1. 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.2. Can I email reports
A.2. DICS has no direct method of emailing reports. However, users can when selecting the 'Print Option' ribbon and 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.3. Can DICS be Used over a Network
A.3. The quick answer is yes. That said, much will depend on how your company network is set-up as to how well DICS will function. DICS 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 (DICS_v#.accdr). This can be achieved running the standard setup file to install DICS on each machine. The installation will link DICS’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 DICS_be.accdb back-end files to a network location where all users can access it, and then delete all the local DICS_be.accdb files. When you start DICS 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 DICS is installed on and run some tests to see how the programme performs from the various locations and with different users accessing DICS at the same time, etc.
Please ensure that DICS 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 DICS has been opened in Read-Only mode. (see Q2)
Q.4. Will DICS work on a 64Bit PC
A.4. 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.5. How do I obtain an unlock code / register my application
A.5. Unlock codes are issued on receipt of the program’s installation code. As each PC will produce a unique installation code (machine footprint), it is for this reason we are unable to issue unlock code until we receive the installation code(s).
The installation code consist of 2 six digit numbers and is offered each time the program is run. Please make a note of the number(s) an forward it to me, indicating which code belongs to which program.
Q.6. Why has the program loaded the relinking routine form?
A.6.The relinking routine normally only appears on non standard installations, i.e. networks or for XP pre SR2.
The program expects to find your data (records) on in the default installation directory on C: Drive. If not found, the semi-automatic relinking routine is loaded to assist the user in locating the source of the data containing files. (i.e. Not every PC will have a C: drive)
Here is a link on how to use the semi-automatic relinking routine for our TIRA application, the principal is the same for all our applications (hosted in Youtube).
On Safe Lines QHSE Software Help file v5.0.09 : Copyright © 2019 Brian G. Welch