KeyACCIDENT: Setup from an existing working client
To set up an installation of KeyACCIDENT from an existing working client, either manually or via a silent deployment option, the following is required:
Please note these steps are performed automatically when installing on client machines with an existing KeyACCIDENT version as part of the built-in upgrade process.
1. Collision database configuration files
An XML configuration file storing the necessary connection settings will exist for each SQL database.
KeyACCIDENT Analysis:
C:\ProgramData\Transoft Solutions\KeyACCIDENT\<Version Number>\Database\<SQLServerName-DatabaseName>.xml
For example:
KeyACCIDENT Data Entry:
C:\ProgramData\Transoft Solutions\KeyACCIDENT Data Entry\<Version Number>\Database\<SQLServerName-DatabaseName>.xml
“Transoft Solutions” will be “Keysoft Solutions” in versions prior to KeyACCIDENT Data Entry 2025
For example:
2. Preferred startup database
If setting for all Windows users on the client machine use HKEY_LOCAL_MACHINE, or HKEY_CURRENT_USER can be used for the current user only.
KeyACCIDENT Analysis:
HKEY_LOCAL_MACHINE\SOFTWARE\Transoft Solutions\KeyACCIDENT\ <Version Number>
LastRunDatabase <SQLServerName-DatabaseName> (string value)
LastRunDatabaseGIS <SQLServerName-DatabaseName> (string value) [1]
KeyACCIDENT Data Entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Keysoft Solutions\KeyACCIDENT Data Entry\<Version Number>
LastRunDatabaseDETemp <SQLServerName-DatabaseName> (string value) [2]
LastRunDatabaseDELive <SQLServerName-DatabaseName> (string value) [3]
3. User authentication database settings (if using KTSUsers)
If setting for all Windows users on the client machine use HKEY_LOCAL_MACHINE, or HKEY_CURRENT_USER can be used for the current user only.
KeyACCIDENT Analysis:
HKEY_LOCAL_MACHINE\SOFTWARE\Transoft Solutions\KtsUSERS\<Version Number>
dbtype SQLServer (string value)
server <SQLServerName/instance> (string value)
KeyACCIDENT Data Entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Keysoft Solutions\KtsUSERS\<Version Number>
dbtype SQLServer (string value)
server <SQLServerName/instance> (string value)
Notes:
[1] A typical setup will direct the Database and DatabaseGIS to the same primary collision and casualty database.
[2] DETemp is a small database to hold new records before they are validated (checked) ready for transfer to the DELive database.
[3] The DELive database is typically the same primary collision and casualty database used for the Database and DatabaseGIS, subject to local workflow preferences.