In the event that some machines on the network have upgraded to a different version of Windows or Access, these directions can be followed to manually install AuditTrail on the newly upgraded machines. These instructions assume a working install already exists and that these instructions are necessary for only a few stations to be upgraded/Installed.
AuditTrail runs a startup routine that allows it to orient itself and make sure it can connect to the data tables properly. There are many different network configurations that could interfere with normal operations. AuditTrail was designed to be as robust as possible given the varying landscape of network topology, operating system variation, and Access version variation.
To be as robust as possible, the best possible scenario is that each user would run a local copy of AuditTrail that is connected to shared data tables. Under some circumstances (due to policy more than technical) this is not possible. In this case, AuditTrail is capable of running in shared mode but is far more prone to corruption and data loss.
The order of operation for AuditTrail start up is as follows:
1. Search for a configuration file in the same directory from which it's started (settings.ini)
If found: load configuration
If NOT found: assume new install and prompt user for required information and create the file
2. Determine if it's running from a network share
If it is: and that's the desired mode (shared mode) then continue
If it is: and that's NOT the desired mode (preferable) prompt the user to install to their machines
3. If running a local copy, verify the version number against the version on the server
If different: prompt user to upgrade
If the same: continue start up routine
4. Make zero or more attempts to relink itself to the data tables to ensure connectivity
5. Load up all current audits and open the Inboxes screen.
While this is not a comprehensive list of all actions taken during start up, this gives the basic overview of what's happening. Other events include: checking if the administrator has taken the database off line, creating appropriate shortcuts, etc.
When AuditTrail starts, it will try to orient itself and ensure that connectivity to the data tables is achieved. Everything from Group Policy, NMCI, ADP, and even MS Access versions and patch levels all contribute to failure modes preventing AuditTrail from bootstrapping properly. Fortunately, many of these automated checks can be manually accounted for but will require the user to understand what's supposed to be happening and how to install it properly. Below are the steps required to perform a manual install.
1. Create a folder on the local computer in the user’s %appdata% folder.
2. From the server, copy the AuditTrail\App\Fe folder and its contents to the newly created folder from step 1.
SPECIAL NOTE: In many cases there can be more files in the Fe folder than the system uses. Some files are created for housekeeping by Access, others are created from various circumstances. The only relevant files are ATFE2.*, settings.ini, and cangelog.txt. While it won't hurt to copy the rest, they are not required.
3. Start AuditTrail by double clicking the ATFE2.accdb file found in the FE folder. You will be presented with a warning from MS Access about trusted locations. Clicking the Enable Content button will allow AuditTrail to start up properly.
4. AuditTrail will automatically create a shortcut on the desktop to be used from now on.
Should you have any questions please contact firstname.lastname@example.org or call 480 427 0391.
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.