Important information regarding the database structure and the correct sharing requirements.
It is necessary to use a mapped drive location that is common to ALL clients that will use the software in a networked environment.
It is essential to backup the database when undertaking ANY administrative tasks such as moving the database or performing a software upgrade.
Database
Locating the database
The location for the database is defined in the registry (taken from the installation of the software initially) under HKEY_LOCAL_MACHINE\Software\Corporate Risk Systems\Settings\Database, if this value is missing then the application folder is assumed by default.
Under no circumstances should you modify the value of this registry key, unless explicitly instructed by CRS Support.
During software startup, a process is executed to load the software environment from the database. If you are part of a corporate network environment, then the user must be granted correct permissions on the section of the registry to ensure the ability to read the location of the database. Please Note: This will be trapped as an Error 13, Type Mismatch during startup. The error is caused by a malformed database location path because the value cannot be read.
See the FAQ for advice on solving this issue.
Ensure all users have permissions to read and modify files contained in the shared folder when moving the database to a network server for multiple user installation.
CRS recommends using mapped drive locations for ease of use and portability. If the server is changed, or the data is moved, a simple modification to the drive mapping will ensure the software continues to function without problems, whilst using the existing details in the configuration.
Reporting
CRS Risk - Risk Assessment Toolkit, uses a Microsoft® Jet Database for the data storage. This is ODBC compliant and can be used with any 3rd party reporting tool, such as Crystal Reports®. If you require assistance with configuring reports using a product such as this, please contact CRS Support for database schema information.
Please Note: CRS assume no liability for damage to data caused by incorrect use of the database. We will endeavour to recover data wherever possible, but please ensure you have good working backups of the database prior to development.
Performance
Over time with continuous modification and deletion of data, the database will become fragmanted and indexes will be slower. You can execute a Compact and Repair process on the database from within the CRS Risk - Risk Assessment Toolkit by following the instructions below:
- Ensure ALL users are currently logged off the software and the database is closed (Tip: If you browse to the folder where the database is located, check for the existence of a lock database file - CRSDATA.LDB. If this file is NOT present then the database is currently closed)
- Backup the database to another folder
- Open a single session and log on as the administrator (SYS)
- Close the corporate profile using the button on the menu bar
- On the main menu, click Maintenance, then Database, then Repair Database
The process is usually very quick and will normally take a few seconds. You can then re-open the Corporate Profile view by clicking the icon in the toolbar (first icon on the left).
If you encounter difficulties connecting to the database after this process, restore the backup file and contact CRS Support.